3 ms·

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

• darkwater 1y 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 1y 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 1y ago
      For me is useful when I run 'git fetch' from the command line. I don't use any graphical git client
  • dewey 1y 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 1y 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 1y 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 1y ago
  gibr makes it super easy to do exactly this!