tweak git authoring
@@ -22,7 +22,7 @@
22
22
- When concrete, complete steps are made, create a commit in that branch as you work
23
23
- Don't wait until everything is finished before you commit, just commit as soon as you complete a step before moving on to the next step
24
24
- Keep commit subjects short and to the point (what changed)
25
- When useful, include a longer commit description body that explains the change in user-facing terms (what users will notice), not only implementation detail
25
- Include a longer commit description body that explains the change in user-facing terms (what users will notice), not implementation detail
26
26
- Try to commit frequently, chunking work into individual steps
27
27
- When all work is done, merge the branch into master using a non-fast-forward merge commit (`git merge --no-ff`), and then delete it so only master remains
28
28
- Ensure you don't leave old branches you've made in git and that everything is merged neatly.
@@ -22,7 +22,7 @@22
- When concrete, complete steps are made, create a commit in that branch as you work
22
- When concrete, complete steps are made, create a commit in that branch as you work
23
- Don't wait until everything is finished before you commit, just commit as soon as you complete a step before moving on to the next step
23
- Don't wait until everything is finished before you commit, just commit as soon as you complete a step before moving on to the next step
24
- Keep commit subjects short and to the point (what changed)
24
- Keep commit subjects short and to the point (what changed)
25
- When useful, include a longer commit description body that explains the change in user-facing terms (what users will notice), not only implementation detail
25
- Include a longer commit description body that explains the change in user-facing terms (what users will notice), not implementation detail
26
- Try to commit frequently, chunking work into individual steps
26
- Try to commit frequently, chunking work into individual steps
27
- When all work is done, merge the branch into master using a non-fast-forward merge commit (`git merge --no-ff`), and then delete it so only master remains
27
- When all work is done, merge the branch into master using a non-fast-forward merge commit (`git merge --no-ff`), and then delete it so only master remains
28
- Ensure you don't leave old branches you've made in git and that everything is merged neatly.
28
- Ensure you don't leave old branches you've made in git and that everything is merged neatly.