On 21/07/2022 12:13, Konstantin Khomoutov wrote: > On Mon, Jul 18, 2022 at 02:34:44PM -0700, Dan Rosen 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? > FWIW, a recent discussion on the main Git list [1] brought to my attention > that there exist support for setting textual branch descriptions: a config > setting branch.<name>.description, which can be manipulated with the > `git branch --edit-description` command. See the gitconfig manual page for > more details. > > 1. https://public-inbox.org/git/[email protected]/
That discussion is looking interesting. However the discussion about Commit-IDs at https://lore.kernel.org/git/[email protected]/ should also be looked at to see some of the nuances that need to be considered (e.g. https://lore.kernel.org/git/[email protected]/). I'm for the idea that it should be possible for branch descriptions to be portable and be passed between repos and devs, but ultimately it is for the local dev to decide which description to accept, use and publish. -- 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/37cea93d-75f3-d7dd-5430-08ac035287e7%40iee.email.
