kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/api/status_checks.md

3.1 KiB
Raw Blame History

stage group info type
Manage Compliance To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments reference, api

External Status Checks API (ULTIMATE)

  • Introduced in GitLab 14.0.
  • It's deployed behind a feature flag, disabled by default.
  • It's disabled on GitLab.com.
  • It's not recommended for production use.
  • To use it in GitLab self-managed instances, ask a GitLab administrator to enable it. (ULTIMATE SELF)

WARNING: This feature might not be available to you. Check the version history note above for details.

List status checks for a merge request

For a single merge request, list the external status checks that apply to it and their status.

GET /projects/:id/merge_requests/:merge_request_iid/status_checks

Parameters:

Attribute Type Required Description
id integer yes ID of a project
merge_request_iid integer yes IID of a merge request 
[
    {
        "id": 2,
        "name": "Rule 1",
        "external_url": "https://gitlab.com/test-endpoint",
        "status": "approved"
    },
    {
        "id": 1,
        "name": "Rule 2",
        "external_url": "https://gitlab.com/test-endpoint-2",
        "status": "pending"
    }
]

Set approval status of an external status check

For a single merge request, use the API to inform GitLab that a merge request has been approved by an external service.

POST /projects/:id/merge_requests/:merge_request_iid/status_check_responses

Parameters:

Attribute Type Required Description
id integer yes ID of a project
merge_request_iid integer yes IID of a merge request
sha string yes SHA at HEAD of the source branch

NOTE: sha must be the SHA at the HEAD of the merge request's source branch.

Enable or disable status checks (ULTIMATE SELF)

Status checks are under development and not ready for production use. It is deployed behind a feature flag that is disabled by default. GitLab administrators with access to the GitLab Rails console can enable it.

To enable it:

# For the instance
Feature.enable(:ff_compliance_approval_gates)
# For a single project
Feature.enable(:ff_compliance_approval_gates, Project.find(<project id>))

To disable it:

# For the instance
Feature.disable(:ff_compliance_approval_gates)
# For a single project
Feature.disable(:ff_compliance_approval_gates, Project.find(<project id>)