There are many repositories in our Project, and I assume it will only increase in number as the number of micro-services go up.
Right now, I need to go to each repository and specify specifics like branch naming, branch restrictions, pull-request defaults, etc. It feels cumbersome in case we decide to change something, and since it has to stay consistent across repositories, we need to go to each repository and make the changes.
Example Use-Case 1:
If we want to change the branch naming convention from feat/ to feature/ and there are 10 repositories in my project, I would have to go to each repository and make this change.
Example Use-Case 2:
If an employee who used to be a default reviewer for repositories leaves, and a new person takes the place, now I need to go to each repository to include the new person as default reviewer.
Announced in this blog, this holiday season we’re celebrating all things CI/CD and between now and the end of 2019 we’ll be showcasing content, use cases, feature announcements and more. One featur...
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