Suppose your Git repository contains numerous branches. The names for branches are supposed to indicate their role, topic and context, but that can become rather unhandy in a large project: main, develop, rewrite_logging, rewrite_logging_again, that_new_feature_we_had_a_coffee_chat_about, urgent111, ...
What are best practices to manage meaningful descriptions of different branches?
That description system should enable people to have an idea of what a branch is about, who worked on that and why; it should avoid people guessing what was the point of a branch.
What are known best practices for this?
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.