Repository navigation
ci: name the reusable CI caller job checks and dispatch CI from force-release - #441
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renames the reusable CI caller job
checktochecks, so the emitted check ischecks / checklike the org's other reusable-CI callers. A pull request opened with the workflow token starts itspull_requestworkflows inaction_requiredwith no jobs, so the requiredchecks / checkis never emitted and the release PR cannot merge without an admin override. The force-release job now approves that held run (POST /actions/runs/{id}/approve), which needsactions: writeon the job (measured: without it the call returns 403). Measured end to end: the approved run reportschecks / checkin the PR's status rollup.