Polishing Your Feature Branch Commits
Polishing Your Feature Branch Commits
Join the DZone community and get the full member experience.
Join For FreeGet the fastest log management and analysis with Graylog open source or enterprise edition free up to 5GB per day
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 usinggit rebase -i HEAD~<num-commits>
The following animated GIF shows how do do it:
Get the fastest log management and analysis with Graylog open source or enterprise edition free up to 5GB per day
Like This Article? Read More From DZone
Published at DZone with permission of Juri Strumpflohner . See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}