Standardizing TeamMentor branching names

I started working on fixing some small issues at TeamMentor with the idea in mind of understanding the branching model that GitHub offers, along with the idea of getting involved with all the workflow at  TeamMentor.

So namely we review the issue list and then we create a branch to address the issue. When it comes to branches, we believe it would be great to standardize it, so all the developers can follow the same pattern. This approach will help us to be all in the same page.

Therefore if you are working in the 235 issue, we believe that we follow the Issue + Underscore + Issue number pattern :

So if you are fixing Issue 235, the name of the branch should be Issue_235.

This approach will help us to track what issue is being addressed in the branch. And it’s important that we are addressing an issue at the time. Having said that, we will have a branch per issue.

This is a small example that will help us to do things better!


About Michael Hidalgo

Michael is a Software Developer Engineer based on San José, Costa Rica. He leads the OWASP Chapter from Costa Rica. You can take a look at my blog at
This entry was posted in Uncategorized and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s