Skip to content

Commit

Permalink
add link to a guide for the micro commits standard
Browse files Browse the repository at this point in the history
  • Loading branch information
henrikvtcodes committed Aug 6, 2024
1 parent 348f1f1 commit 3c572eb
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions docs/verso-standards/micro-commits.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,14 @@ To illustrate the process of micro-committing, here's a hypothetical situation w
3. **Make the code pretty:** Formatting, refactoring, etc. Things that make your code easier to read and fix at a later date. Commit after this is done, fixing any errors that cropped up beforehand.
4. Push to remote! (If you haven't already)

A good detailed guide: [A Practical Guide to Micro Commits | Niko Heikkila](https://world.hey.com/niko.heikkila/a-practical-guide-to-micro-commits-a37151eb)

## Why?

Many developers tend to make large, infrequent commits full of unrelated changes. This can make it hard to track how a project has evolved or how different parts of a codebase have changed. Some benefits include:

- **Reducing risk of losing work:** Frequently committing and pushing means that your work gets incrementally saved
- **Debugging via commits:** As you fix bugs or develop new features, small commits allow you to figure out (and revert) exactly what changes might be causing errors
- **Reducing risk of losing work:** Frequently committing and pushing means that your work gets incrementally saved.
- **Debugging via commits:** As you fix bugs or develop new features, small commits allow you to figure out (and revert) exactly what changes might be causing errors.
- **Merge conflict resolution:** Resolving merge conflicts can be made easier via micro-committing, since the git merge algorithm has more information to work with.

## More information
Expand Down

0 comments on commit 3c572eb

Please sign in to comment.