regression check
@@ -24,6 +24,7 @@
24
24
- Keep commit subjects short and to the point (what changed)
25
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
- When making commits, ensure you're not accidentally reverting newer code with an old snapshot.
27
28
- 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
29
- Ensure you don't leave old branches you've made in git and that everything is merged neatly.
29
30
- Always run the full test suite and fix any issues (including unrelated to your work) before merging to master.
@@ -24,6 +24,7 @@24
- Keep commit subjects short and to the point (what changed)
24
- Keep commit subjects short and to the point (what changed)
25
- Include a longer commit description body that explains the change in user-facing terms (what users will notice), not 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 making commits, ensure you're not accidentally reverting newer code with an old snapshot.
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
- 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.
29
- Ensure you don't leave old branches you've made in git and that everything is merged neatly.
29
- Always run the full test suite and fix any issues (including unrelated to your work) before merging to master.
30
- Always run the full test suite and fix any issues (including unrelated to your work) before merging to master.