←back to thread

Git CLI tool for intelligently creating branch names

(github.com)
35 points Terretta | 1 comments | 31 Oct 25 13:37 UTC | HN request time: 0.236s | source
Show context
celticninja ◴[31 Oct 25 16:20 UTC] No.45773798[source]▶
I think branch names are quite unimportant in development and often don't worry about them being too descriptive.

In my org it is common to use the JIRA ticket number in there somewhere but other than that I think you should leave it up to devs. I can't think of a reason why I would need to know the branch name.

My favorite branch name I created was for a JIRA ticket with the number 2468.

This became ab-2468-who-do-we-appreciate

Detailed branch naming conventions are just another piece of useless documentation for devs. And if you are using the branch name to tell you what is going on the you are misunderstanding the review process.

replies(1): >>45783989 #
1. ytreister ◴[01 Nov 25 18:22 UTC] No.45783989[source]▶
When you use Gitlab and squash your merge request, a new merge commit with the name of the branch is created, so I found it very helpful in that situation to know the name of the branch.