Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,249
Community Members
 
Community Events
176
Community Groups

Feature suggestion: Default repository configuration at Project level

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.

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events