Set the scopes for a commit
Set the scopes a commit impacts.
Prefer this over the pull request variant. Scopes computed for one revision do not describe another, so naming the revision lets a report be matched against the head a pull request actually has. A report for a revision a pull request has already moved past can no longer overwrite what its current head reported; a report is still applied to every open pull request whose head it currently is, which is the normal case.
A report replaces the previous one for that revision in full: all_scopes defaults to false, so omitting it clears a barrier previously reported for the same commit. Send the complete result of your scope computation every time.
Send the pull request's head SHA (github.event.pull_request.head.sha). That is not always the revision your job checked out: on a pull_request event the default checkout is a merge commit, and a report keyed on that SHA matches no pull request head.
Path parameters
The commit SHA the scopes were computed from
The commit SHA the scopes were computed from
The owner of the repository
The owner of the repository
The name of the repository
The name of the repository
Request body
Response
Successful Response
Changes
Changed in 1 of the 11 revisions of this API.1
- ○
endpoint added
endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○