What is best practice to name a branch of epic

Ranjan_Tiwari April 29, 2020

I am working on a project, where i used to work many users stories of a epic, so we follow below process for release the feature.

 

1. clone development branch

2. Create epic branch from development. For e.g., epic/SLx-x

3. Create feature branch from epic branch. For e.g, feature/SLx-x

4. Merge feature branch into epic branch

5. Merge epic branch into development

6. Merge development into staging

7. So on to production

My question is what is best practice name a epic branch? is epic/SLx-x is correct naming style?

1 answer

2 votes
Nikki Zavadska _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 2, 2020

Hi,

we're using a similar process and naming convention. Using epic/[issue key number] and feature/[issue key number] (eg. epic/SWAN-123, feature/SWAN-124) should do it :)

You also can always refer back to the Jira issue quickly which turned to be useful more than once during testing, debugging and automation.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events