Road to project success with Git: An Another Git Workflow

Road to project success with Git: An Another Git Workflow

Git is for a long time my favorite version-control system. I use it in almost all of my projects, and I really can’t do without it. Today, I would like to share with you my way of managing projects with this excellent tool. Git is easy to use but can be extremely powerful when used properly.

Based on my different experiences (Freelance work, school project, hackathon…), this article is for people who already have the basics of Git. I invite complete beginners to read this excellent article written by Anne Bonner. For more details about commands, I invite you to read the Git Reference Manual.

Before introducing my Git workflow, let me define five rules:

  • The main branch for development is the branch called develop
  • The project must be divided into as many features as possible, so there will be ONE branch per feature.
  • Avoid unnecessary new commits (which does not add new features)
  • Branches for adding new features have the suffix feature/ and branches for fixing and patches have the suffix fix/.
  • Do not merge directly into develop, the merge of a feature must usually be done by a developer of the team, so you have to make a pull request.

Now that the rules have been defined here is my workflow:

My Git Workflow

The use of this cycle will ensure good management of your project. Contact me if you have any suggestions, I would be happy to improve my model.


Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now