←back to thread

Git CLI tool for intelligently creating branch names

(github.com)
35 points Terretta | 2 comments | 31 Oct 25 13:37 UTC | HN request time: 0.001s | 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 #
alkonaut ◴[31 Oct 25 15:52 UTC] No.45773466[source]▶
having feature/username/id-desc is good though. Because at least you can identify why the branch is there. That they are ephemeral doesn't mean that people actually clean them up...
replies(2): >>45774889 #>>45784386 #
1. delusional ◴[31 Oct 25 18:05 UTC] No.45774889[source]▶
Either it has commits I care about or it doesn't. Either way, I'm not going to consult the branch name.

If it has commits I care about, then it stays. If it doesn't, It goes. I'm only deleting on the server afterall, people can just push it back.

replies(1): >>45788511 #
2. ytreister ◴[02 Nov 25 07:30 UTC] No.45788511[source]▶
I understand, but that means you need to review the commits and code changes and do not have the context which could be found either in the issue title, description, etc.