Member-only story
Git Flow, Customized and Explained
How to work effectively with Git repositories in enerprise projects — a well-tried way
How to work with real-world Git repositories effectively? How to track information about what is currently in production, what is being developed and what is going to be released next? How to simultaneously work on a current release and features for future releases? These and other questions are addressed below. Stay tuned!
Good or bad, everybody talk about Git flow, but who really follows every recommendation? Every project has its own face, and the common denominator doesn’t always work. In this blogpost I’d like to share an approach to the classic Git flow that worked for me and that I’ve tested with not one repository.
The original version of the flow was introduced back in 2010 as A Successful Git Branching Model.
Description
Let’s start with brief description of each branch involved.
main
(Formerly known as master,) this branch contains finished, tested and ready to production code. New releases are built from this branch.
If there’s no release planned for the nearest future this branch contains the latest production version of the application.
