←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.202s | source
Show context
r1cka ◴[31 Oct 25 14:56 UTC] No.45772653[source]▶
I think people worry too much about branch names. Feature branches are usually ephemeral. Prefix your branch with your personal identifier so I know who is primary on it and worry more about the commit message which will live on indefinitely.
replies(5): >>45772677 #>>45773377 #>>45773466 #>>45774133 #>>45774578 #
morkalork ◴[31 Oct 25 14:57 UTC] No.45772677[source]▶
Yes, please just name the branch after the ticket/issue number so we can all get the context for it and call it a day
replies(3): >>45772963 #>>45773320 #>>45784312 #
wara23arish ◴[31 Oct 25 15:15 UTC] No.45772963[source]▶
I hate issue numbers for branch names. ISSUE-9482 doesn’t really provide much.

Ticket link should always be included in PR description.

But branch names should be descriptive like terraform_dev_create_instance

etc

replies(3): >>45773128 #>>45773171 #>>45784316 #
jjgreen ◴[31 Oct 25 15:29 UTC] No.45773171[source]▶
I've worked in a couple of places with <issue ID>-<something descriptive> conventions, moderately useful
replies(2): >>45773317 #>>45775386 #
krferriter ◴[31 Oct 25 15:41 UTC] No.45773317[source]▶
Yes, `issue-10-add-feature-X` style is best.
replies(1): >>45774811 #
1. bavent ◴[31 Oct 25 17:57 UTC] No.45774811[source]▶
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.