ci: use a PAT for release-please and post manifest diff comments - #15
Merged
Conversation
diff-action v2 only formats the diff and sets an output; it no longer posts the comment itself. Post it with int128/comment-action, replacing the previous comment on each push.
The org policy does not allow the built-in GITHUB_TOKEN to create pull requests, and a PAT-created release PR also gets normal PR validation (GITHUB_TOKEN events never trigger other workflows). Falls back to GITHUB_TOKEN when the RELEASE_PLEASE_TOKEN secret is not configured.
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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.
Why
Two CI fixes from the #14 branch were pushed a few minutes after that PR was merged, so they never landed on main:
After merging
Trigger the Release Please workflow once (it has workflow_dispatch) or wait for the next push to main. It will open the "release trilium 2.0.0" PR using the PAT, with the changelog built from the feat! commit in #14.