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,466,419
Community Members
 
Community Events
176
Community Groups

How can I efficiently get the number of commits a branch is ahead/behind using the REST API?

Edited

I'm trying to build reporting around branches' relative histories, so that we can:

  • See what branches have been merged to the upstream branch and can be removed
  • See what branches have commits that need to be merged to the upstream branch
  • See what branches need to be merged from upstream in order to avoid conflicts when merging to upstream

Basically I want the same ahead/behind info that's shown in the Web UI's Branches page for a repo, but I need to automate reporting on it for multiple repositories at once.

Right now I have a working process via:

  1. Get list of repos
  2. For each repo, get list of branches
  3. For each branch, get list of commits on that branch with ?exclude=<upstream> to see how many commits ahead it is
  4. For each branch, get list of commits on the upstream branch with ?exclude=<branch> to see how many commits behind it is

This works, but rapidly hits the 1k/hr rate limit on calls to the commits route, and it's horribly slow with more than a handful of repos & branches, and worse yet with multiple pages of commits as the paginated commits API does not provide a full result set count. I understand the rate limits, and for the performance on both ends I would much rather a cleaner way of doing this, but I can't find any other option anywhere in the SDK docs. Have I missed something?

4 answers

+1

Same question, same problem.

Why this feature available on Web UI is not available into API.

Absolutely a must feature.

We are highly interested in this. 

Any possible availability in near upcoming releases?

+1 here. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events