Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
You need to sign in or sign up before continuing.
  • gitlab-ce
  • lib
  • api
  • branches.rb
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Fix API /project/:id/branches not returning correct merge status · cedbb336
    Stan Hu authored Mar 29, 2019
    https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24034 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.
    
    Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56250
    cedbb336
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7