How do you name your git branches?

Michael Lee 🍕 - Dec 19 '18 - - Dev Community

I'm currently evaluating an alternative to Jira for managing our software development projects at work. One of the things that I'm having a hard time moving away from is Jira's ability to have keys and auto incrementing ID for each task/issue.

So let's say I've got a DEV.to project setup, I could set a key as DEV and each issue I create will have a prefix of DEV-. Currently we will use this key and ID combination to also name our git branches in source. So if the issue is 23, then our branch would be cut as DEV-23 and then it's easy for us to track from VCS to Jira to PRs on BitBucket.

But as I'm evaluating alternatives, I'm realizing this key/id might be unique to Jira or software development management tools.

So my question is, if there is no key or ID and you're working across multiple projects, what sort of naming scheme do you use for your git branches?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player