"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.
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.
"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.