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?
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.
Most of us are probably pretty familiar with traditional Retrospectives. But we’ve got another variation for you to try – and we think you’ll really like it! It’ll not only help you make room for doi...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events