I believe this has been discussed a few times. However branches are meant 
to be local and ephemeral, which goes against that 'organise' view that, in 
a sense, sees branches as tasks to be controlled. 

Git, being distributed, looks to the code content, along with the DAG, to 
get it's perspective on the code. Once a branch has been merged, where 
would the meta data go (and who decides)?

On Monday, July 18, 2022 at 10:34:44 PM UTC+1 [email protected] wrote:

> Adding metadata to branches would be helpful for third party APIs to 
> organize and tag branches without putting them in the branch name. For 
> example, project management software will use an issue key to search the 
> branch name but it would be better to search branch metadata. I know 
> branches have descriptions but I believe these are part of the local 
> configuration?
>
> - Dan Rosen
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/62f625ec-1a6c-4dde-aad8-2ac438eb1b45n%40googlegroups.com.

Reply via email to