6 ms·

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 shoul

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

6LLvveMx2koXfwn 11mo ago
we do: [feature/bug]/ISSUE-NUMBER-summary-of-issue e.g.: bug/psi-456-broken-args-parsing
- darkwater 11mo ago
  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.
  - celticninja 11mo ago
    But the PR and git blame can tell you this so I would never look at the Branch name to find out this information
    - darkwater 11mo ago
      For me is useful when I run 'git fetch' from the command line. I don't use any graphical git client
  - dewey 11mo ago
    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.
  - ytreister 11mo ago
    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 https://github.com/ytreister/gibr/issues/42
    - ytreister 11mo ago
      I implemented this in version 0.6.0 which was just released. https://github.com/ytreister/gibr/releases/tag/0.6.0 https://github.com/ytreister/gibr/releases/tag/0.6.0 The issue assignee can be used in the branch name.
- ytreister 11mo ago
  gibr makes it super easy to do exactly this!
jjgreen 11mo ago
I've worked in a couple of places with <issue ID>-<something descriptive> conventions, moderately useful
- krferriter 11mo ago
  Yes, `issue-10-add-feature-X` style is best.
  - bavent 11mo ago
    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.
- johntash 11mo ago
  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.
ytreister 11mo ago
gibr makes it easy to do this and in a consistent manner

6LLvveMx2koXfwn 11mo ago

we do: [feature/bug]/ISSUE-NUMBER-summary-of-issue e.g.: bug/psi-456-broken-args-parsing

darkwater 11mo ago
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.
- celticninja 11mo ago
  But the PR and git blame can tell you this so I would never look at the Branch name to find out this information
  - darkwater 11mo ago
    For me is useful when I run 'git fetch' from the command line. I don't use any graphical git client
- dewey 11mo ago
  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.
- ytreister 11mo ago
  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 https://github.com/ytreister/gibr/issues/42
  - ytreister 11mo ago
    I implemented this in version 0.6.0 which was just released. https://github.com/ytreister/gibr/releases/tag/0.6.0 https://github.com/ytreister/gibr/releases/tag/0.6.0 The issue assignee can be used in the branch name.
ytreister 11mo ago
gibr makes it super easy to do exactly this!

jjgreen 11mo ago

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

krferriter 11mo ago
Yes, `issue-10-add-feature-X` style is best.
- bavent 11mo ago
  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.
johntash 11mo ago
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.

ytreister 11mo ago

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