Git Flashcards
https://vimeo.com/280579162
1
Q
Why should you build novel length commit messages?
A
Commit messages should show WHY a change was made. Remember about the in-memory ordering caused by a default ordering in an ActiveRecord model that was removed after a while, but no one removed the in-memory ordering. https://vimeo.com/28AC0579162
2
Q
Should you use git commit -m
A
No, the command line is not the place to write long commit messages explaining why a change was made.
3
Q
What is better than git blame?
A
The pickaxe:
git log -S snippet_of_code
4
Q
What is important in a commit message?
A
Explaining the WHY
NOT the what
5
Q
Should you leave not valuable commits in history?
A
No, treat your commits as mutable. Use amend and rebase.
