Task: For branches which are neither features nor fixes.Docs: For branches related to markdown or release documents.I found myself adding two more folders to my Gitflow repos: So basically, a GitFlow organization would have these three folders:Īs there is no public document talking about this, I've seen some working copies using those folders in plural and others in singular. That being said, Let's explore some ways of organizing branches, so you don't get lost in a sea of code.Īlthough Gitflow doesn't mention branch folders, many devs use "Feature branches", "Hotfix branches" and "Release branches" and create folders accordingly. You will see this implemented in many UI clients, but I never found it on console clients, or on websites like Github or GitLab. But, this past year, I've been influenced by many developers from the community, and started using git in different ways depending on the projects I was working on.īefore getting into the different branching styles, it's important to remember that, although many git clients treat slashes ("/") as a directory separator, there is no such thing as folders or directories in the git specification. Since then, I've been following the "Git Flow" style. At that time, A successful git branching model by Vincent Driessen was required reading if you wanted to learn how to work with git effectively.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |