top | item 45772963

(no title)

wara23arish | 4 months ago

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

discuss

order

jjgreen|4 months ago

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

krferriter|4 months ago

Yes, `issue-10-add-feature-X` style is best.

johntash|4 months 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.

6LLvveMx2koXfwn|4 months ago

we do:

  [feature/bug]/ISSUE-NUMBER-summary-of-issue
e.g.:

  bug/psi-456-broken-args-parsing

darkwater|4 months 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.

ytreister|4 months ago

gibr makes it super easy to do exactly this!

ytreister|4 months ago

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