-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add guidance on making commits atomic #696
Conversation
It's really long, and uses H5 headings. Any new section would result in unreadable H6s.
3c2f684
to
0017f21
Compare
I think atomic commits are very useful, especially in how it helps makes reviewing clearer when stepping forwards and backwards through the commits whilst still having a (hopefully) working branch. I added a small suggestion to make the description of what an atomic commit is a bit clearer. |
For easier reading. Co-authored-by: Ian James <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super! Thanks also for tidying up the rest of the section 👍
Thanks @injms! |
Most developers are very good at making their commits granular/atomic. But it takes practise and isn't currently our recommended way. It should be something that we strive for.