First things first – merging pull requests in order

When it comes to getting the next release out and deployed – more often than not things don’t go as smooth as you wish. There’s a last-minute bugfix and another feature just got finished, plus there is a bug in production that needs to be fixed immediately.

If your team is using a source code branching model that’s close to Git flow – all of the above should not be a problem.

As always, prioritizing pull request merges to ship the hotfix, the bugfix and perhaps even the new feature in the upcoming release is key to stay on top of the release process.

First things first! With Organizr pull request merge hierarchy release managers and their team can make sure pull requests are merged in order of priority.

(1) Top priority – that hotfix needs to go into production

(2) The hotfix also needs to be merged with develop to avoid drift between develop and master

(3) That feature the team’s been working on is ready to be merged to develop

(4) Feature and bugfix can be merged to release for QA testing

(5) The feature can is shipped to production

Here is a short clip that shows Organizr pull request merge hierarchies in action

 

No more merge chaos in Bitbucket!

Install Organzir for Bitbucket now to structure your pull request merge process and bring your team on board!