Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39,511
    • Issues 39,511
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,221
    • Merge requests 1,221
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #13712

Closed
Open
Created Aug 22, 2019 by Patrick Bajao@patrickbajaoMaintainer

Public API endpoint for getting approval state of merge request with multiple approval rules

Problem to solve

API user can't check the approval state of each approval rule.

Intended Users

Developers

Further details

We have an existing private API endpoint (GET /projects/:id/merge_requests/:merge_request_iid/approval_settings) which returns the approval state of merge request for each approval rule. This is being used by the web UI but no equivalent on the API.

Proposal

As discussed in https://gitlab.com/gitlab-org/gitlab-ee/issues/12055#note_205671665, we should make the existing private API endpoint mentioned above public and change its path to /approval_state to be more explicit and consistent with the naming in our code (ApprovalState model).

Also rename the approvers property in the response as eligible_approvers.

Permissions and Security

Permissions of the API should be consistent with interface permissions of the user performing the operation.

Documentation

Update the Approvals API documentation

Edited Aug 28, 2019 by Patrick Bajao
Assignee
Assign to
Time tracking