Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Polishing Your Feature Branch Commits

DZone's Guide to

Polishing Your Feature Branch Commits

· DevOps Zone ·
Free Resource

The need for DevOps innovation has never been greater. Get the results from over 100 business value assessments in this whitepaper, Digital Darwinism: Driving Digital Transformation, to see the positive impact of DevOps first hand.

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:

Demo on cleaning up your commit history ( enlarge)

Interested in Kubernetes but unsure where to start? Check out this whitepaper, A Roundup of Managed Kubernetes Platforms from Codeship by Cloudbees, for an overview and comparison of Kubernetes platforms. 

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}