Repository navigation
Fix: authenticate the template update as the release app - #102
Merged
Merged
Conversation
The workflow opened its pull request with GITHUB_TOKEN, which starts no checks, so the pull request could only be merged by bypassing the ruleset. Document creating the app the release now depends on.
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.
Summary
ca-template-changes.ymlas the release app instead ofGITHUB_TOKEN, so the template pull request it opens starts its checks.contents: writeandpull-requests: writetopermissions: {}, and remove the matching entry from the workflow permission allow-list.docs/releasing.md: permissions, private key, installation, and the two secret names.Testing
All green. Extended 2 existing tests to the template workflow.
Checklist