1.3 KiB
| title | date | permalink | tags | cta | snippet | drupal_planet | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| No-one sees your clean-up commits | 2024-09-02 | daily/2024/09/02/no-one-sees-your-clean-up-commits |
|
d7eol | No-one sees your clean-up commits. | true |
When you're working on a task - whether you're making it work or making it good, you can commit your code changes as often as you like.
You should definitely commit your changes every time you have a working iteration, even if it's not the complete or final version, or even if the code doesn't pass all the coding standards and static analysis checks.
Things can be fixed or improved in subsequent commits.
You can amend or squash commits locally so your clean-up and work-in-progress commits are removed before you push your final version to your remote repository.
Whilst test-driven development says you should work in small feedback loops and steps, you don't need to push every commit as you wrote them.
Until you run git push, your commits are yours and yours only.
You have the opportunity to tidy up and organise your changes - making your commits easier to review and more likely to be approved in a code review.