aboutsummaryrefslogtreecommitdiff
path: root/blog/content/notes/tech/git-advice.gmi
diff options
context:
space:
mode:
Diffstat (limited to 'blog/content/notes/tech/git-advice.gmi')
-rw-r--r--blog/content/notes/tech/git-advice.gmi21
1 files changed, 21 insertions, 0 deletions
diff --git a/blog/content/notes/tech/git-advice.gmi b/blog/content/notes/tech/git-advice.gmi
new file mode 100644
index 00000000..8ec41105
--- /dev/null
+++ b/blog/content/notes/tech/git-advice.gmi
@@ -0,0 +1,21 @@
+# Git advice
+
+## Never use "git commit -m", use "git commit -v"
+
+Configure your system so that the EDITOR environment variable refers to your preferred editor.
+
+With "git commit -v" you can see your commit diff while writing your commit message. This helps you review that your commit is correct and write a better commit message.
+
+## Use gitignore properly
+
+=> https://git-scm.com/docs/gitignore gitignore
+
+Note that by default, Git defaults to $XDG_CONFIG_HOME/git/ignore or $HOME/.config/git/ignore.
+
+## Use the modern Git commands (or teach them)
+
+Particularly, "git checkout" has many functionalities that now can be handled by more focused commands like "git switch" and "git reset".
+
+If you have too much muscle memory and are used to them, then consider learning them only to teach other people so that they start with the safer commands.
+
+Many Git commands print suggestions that use the newer commands.