The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

API for getting commits returns inconsistent results

Jere Jones
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 4, 2020

I'm using the V2 API to get the commits that are in develop but not master.  The URL I'm using is similar to this:

GET https://api.bitbucket.org/2.0/repositories/owner/reposlug/commits/?exclude=master&fields=next%2Cpage%2Cvalues.author.user.uuid%2Cvalues.message%2Cvalues.summary.html&include=develop

I have also tried this:

GET https://api.bitbucket.org/2.0/repositories/owner/reposlug/commits/develop?exclude=master&fields=next%2Cpage%2Cvalues.author.user.uuid%2Cvalues.message%2Cvalues.summary.html 

Sometimes, it will return the correct commits (for my test case, about 675 commits).  Most of the time, it will return every commit on develop back to the initial commit (about 14,000 commits). 

I have captured the outputs and sometimes page 7 has no next field.  Most of the time it does.  Even when the ctx param is the same (although I have only captured that situation once).

 

I expect a response that would be equivalent to the following command:

git log develop ^master

 

I'm at a complete loss.  Any help would be very much appreciated.

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

TAGS
AUG Leaders

Atlassian Community Events