ci: say what to do when the release PR can't be opened - #21
Merged
Conversation
v1.0.10 published to npm and tagged, then the workflow died on `gh pr create` with "GitHub Actions is not permitted to create or approve pull requests", which left master a version behind the registry. That repo setting is off by default and is now on. GITHUB_TOKEN has no permission scope that can read that setting, so the workflow can't check it before publishing. The step now prints the branch to open a PR from and the setting to turn on, instead of leaving a bare GraphQL error in the log.
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
1 participant
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.
Turns a bare GraphQL error into instructions when the release workflow can't open its bump PR.
v1.0.10 hit this: it published to npm and pushed the tag, then died on
gh pr createwith "GitHub Actions is not permitted to create or approve pull requests", so master sat a version behind the registry until I opened #20 by hand. The repo setting behind it is off by default and is now on.Checking the setting before publishing isn't possible.
GITHUB_TOKENhas no permission scope covering repo Actions settings, sogh api repos/:repo/actions/permissions/workflowreturns 403 from inside a workflow. The step now reports the pushed branch and the setting to turn on, and says to merge with a merge commit rather than a squash.