See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
/* | |
##Device = Desktops | |
##Screen = 1281px to higher resolution desktops | |
*/ | |
@media (min-width: 1281px) { | |
/* CSS */ | |
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="UTF-8" /> | |
<title>Add React in One Minute</title> | |
</head> | |
<body> | |
<h2>Add React in One Minute</h2> | |
<p>This page demonstrates using React with no build tooling.</p> |
#include <Servo.h> | |
Servo myservo; | |
const int servoPin = 9; | |
const int buttonPin = 12; | |
const int ledPin = 13; | |
void setup() { | |
myservo.attach(servoPin); |
Here’s how to make animations like this one. It requires intermediate Unix command-line knowledge, to install some tools and to debug if they don’t work. You’ll need these utilities:
curl
(or you can translate to wget
)convert
and montage
, part of ImageMagickffmpeg
, plus whatever codecsparallel
, for iteration that’s nicer than shell for loops or xargs
zsh
for leading 0s in numerical ranges to workbuild
: Build related changes (e.g npm related/ adding external dependencies)
chore
: A code change that external user won't see (eg: change to .gitignore file or .prettierrc file)
feat
: A new feature
fix
: A bug fix
docs
: Documentation related changes
refactor
: A code that neither fix bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name)
perf
: A code that improves performance
style
: A code that is related to styling
test
: Adding new test or making changes to existing test
/* Windows */ | |
{ | |
"blocks": [ | |
{ | |
"type": "prompt", | |
"alignment": "left", | |
"segments": [ | |
{ | |
"type": "os", | |
"style": "plain" |
oh-my-posh --init --shell pwsh --config ~fullPathHere\justinbalaguer.omp.json | Invoke-Expression | |
#change fullPathHere to path of .omp.json file |