Repository navigation
ci(release): open release prs with the release bot app - #119
Merged
Merged
Conversation
Contributor
Test results 249 files 249 suites 1m 3s ⏱️ Results for commit 0dfd5e8. |
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.
Proposed changes
Release PRs opened by this repository's release workflow never got their checks running. The default token leaves every check on them waiting for approval that nobody gives, and GitHub fails them after 30 days, which posts a stream of failure notifications to Discord. Release PRs are now opened by the onelitefeather-release-please-bot app, the same setup Titan uses, so their checks run normally and get the same review as any other change. Only the token changes; release creation and publishing stay as they were.
Type of change
Checklist
./gradlew build testpasses locally