Polish my git feature branch before merging or submitting for review
It is a good practice to commit as often as possible while you work on your personal feature branch. That helps you trace your changes as well as to have a backup to jump back to in case something goes wrong terribly. However such git branches with dozens of commits (that may not make sense) are hard to merge and review. In this lesson we’re using an “interactive rebase” to adjust our git history.
I really appreciate how this course is providing useful examples and also mentioning best practices for devs. It's great knowing that I can take the time to go back and polish things up before having the code reviewed.
I've mostly been working independently on projects, so this thankfully helps me understand the importance of being mindful of my coding style and organization. Then after working on a contract, others who get hired later on can benefit from the effort I put in to learn how to properly organize my work.
@Erik thanks so much for the nice feedback 😊