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,458,233
Community Members
 
Community Events
176
Community Groups

Conditional Limiting of Remote Repo Updates

In our company we have a lot of git repositories hosted on AWS CodeCommit, and we have recently been noticing rate-limit excess on AWS. Upon closer inspection it seems like a huge number of calls are originating from my Sourcetree installation. I have adjusted the remote update frequency to hourly however this still does a load of calls (1,000+ / day) to refresh all my tracked repositories.

If possible I would very much like the option to limit the updating to just the repositories that are open in tabs (ie. the ones that are being worked on - rather than the ones just lying around). One other possible option might be to have the option present for every repository - whether to check for updates or not, although this would mean that more manual configuration updates are necessary every time that you move on to another project.

In the mean time I can reduce the update frequency even more, but it will soon reach a point where it would no longer be necessary for it to check for updates on my behalf.

Thanks for your time.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events