I've worked in a couple of places with <issue ID>-<something descriptive> conventions, moderately useful

Yes, `issue-10-add-feature-X` style is best.

I have a little script that does this automatically - lists out Jira tickets assigned to me, then when I select one, creates a branch with the ticket number and the title, subbing hyphens for spaces and truncating if needed. It’s handy for when I want to list branches, I can filter on keywords I remember from the ticket name.

That's been my preference at most places I've worked. issue id so the branch gets linked to jira or whatever and a short description to find the branch later if needed.

we do:

  [feature/bug]/ISSUE-NUMBER-summary-of-issue

e.g.:

  bug/psi-456-broken-args-parsing

More or less the same here, but we (I?) prefix it with the username as well, so when pulling branches you know who created it.

I added a new TODO issue so that username can be configured in the branch name. gibr currently does not have support for username.

https://github.com/ytreister/gibr/issues/42

I implemented this in version 0.6.0 which was just released. https://github.com/ytreister/gibr/releases/tag/0.6.0 The issue assignee can be used in the branch name.

A nice benefit of prefixing by your-name/issue-1234-some-description is that many git clients will show it in a folder structure that way and it's easy to differentiate yours from other branches.

But the PR and git blame can tell you this so I would never look at the Branch name to find out this information

For me is useful when I run 'git fetch' from the command line. I don't use any graphical git client

gibr makes it super easy to do exactly this!

gibr makes it easy to do this and in a consistent manner