That way, it's clear that this branch has production-ready code
What if it's not code that I'm keeping in my repo? For example I kept my masterprincipal thesis in git. At that time, still in school, I felt no connection to the word prod at all. I think the premise for this discussion is absurd, but if I had to pick a new word, it would have to be as generic as possible. I think main works well.
"As generic as possible" would probably be "default", because that's all it is. It's the default branch.
It might be for production code. It might be for in-development code. It might be for documentation. It might be for something completely different.
Folks using git should choose a name for their first branch that accurately reflects what the branch is being used for. That way it's not ambiguous.
And if you're using it just for yourself, and not using it for collaboration, so it doesn't matter what you call it, call it whatever you want. It doesn't affect anybody else. It only has to have meaning to you.
What if it's not code that I'm keeping in my repo?
While "production" may not be a 100% accurate word (and is why different people have different ideas for the default name), the concept is still the same -- that's the rendition that's going to ultimately go to the final audience (be it client computers or bookshelves).
Weirdly enough, all of this disagreement could be solved by making the default branch name a config option...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What if it's not code that I'm keeping in my repo? For example I kept my
masterprincipal thesis in git. At that time, still in school, I felt no connection to the wordprodat all. I think the premise for this discussion is absurd, but if I had to pick a new word, it would have to be as generic as possible. I thinkmainworks well."As generic as possible" would probably be "default", because that's all it is. It's the default branch.
It might be for production code. It might be for in-development code. It might be for documentation. It might be for something completely different.
Folks using
gitshould choose a name for their first branch that accurately reflects what the branch is being used for. That way it's not ambiguous.And if you're using it just for yourself, and not using it for collaboration, so it doesn't matter what you call it, call it whatever you want. It doesn't affect anybody else. It only has to have meaning to you.
While "production" may not be a 100% accurate word (and is why different people have different ideas for the default name), the concept is still the same -- that's the rendition that's going to ultimately go to the final audience (be it client computers or bookshelves).
Weirdly enough, all of this disagreement could be solved by making the default branch name a config option...