18
Branching strategy for a text based project
(feddit.it)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Mar 2025
18 points (100.0% liked)
Git
4740 readers
1 users here now
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Resources
Rules
- Follow programming.dev rules
- Be excellent to each other, no hostility towards users for any reason
- No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.
founded 3 years ago
MODERATORS
Sounds like a fine usecase for git.
I don't know the structure of your work, and there is not one correct way to do things.
"Too short" branches would be when you open and merge into main multiple times a day. "Too long" branches would be when one person works on their own branch for months without checking the whole.
In software, before merging into main, it's customary to have a person other than the author review and (dis)approve the changes.
Thank you for your reply! What are the "objects" possibly determining a branch? Features? Chapters? Writers? Releases?
The first commit on main would be a rough structure of the document.
Then branches for each feature (in your case perhaps "abstract", "chapter 2: intro" "chapter 2: methodology" "chapter 2: conclusion"), and branches for bugs (in your case perhaps: "proofreading and errata chapter 2", "correct legend figure 4.2").