|
|
|
|
|
by phailhaus
2206 days ago
|
|
Yup. It's also an unreasonable burden to be asked to architect your commits so perfectly that each commit is an atomic change, especially since you're often iterating and trying different approaches. The only method that consistently results in atomic commits is to squash commits when merging, in which case the commit message is your PR title/contents. The nice side effect is that these messages should absolutely be readable since your audience was your code reviewers. |
|