by
Join the DZone community and get the full member experience.
Join For Free
when you create your own, personal feature branch you're allowed to do as much commits as you want, even allowing kinda dirty commit messages. this is a really powerful approach as you can jump back to any point in your dev cycle. however,
once you're ready to merge back to master
you should polish your commit history by doing a rebase. this is done using
git rebase -i head~<num-commits>
the following animated gif shows how do do it:
Published at DZone with permission of Juri Strumpflohner. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments