Skip to content

Fix API /project/:id/branches not returning correct merge status

Stan Hu requested to merge sh-fix-project-branches-merge-status into master introduced a regression where only the first 20 branches were used to determine whether a branch has been merged because the pagination was applied incorrectly. Requesting the second page of branches via the API would always have the wrong merge status. We fix this by properly paginating the branches before requesting their merge status.


Merge request reports