ci: use gh app to generate token rather than classic token#35
Merged
kelly-sovacool merged 2 commits intomainfrom Mar 10, 2026
Merged
ci: use gh app to generate token rather than classic token#35kelly-sovacool merged 2 commits intomainfrom
kelly-sovacool merged 2 commits intomainfrom
Conversation
Contributor
|
@kelly-sovacool ... Done! Please check. |
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.
Changes
Switch from using a classic token for gh authentication to generating one with the CCBR-bot app.
@kopardev can you install the CCBR-bot and set the app ID variable and private key secret for each of these organizations? instructions here: https://ccbr.github.io/actions/gh-app-auth.html
Issues
see also NCI-RBL/.github#1
PR Checklist
(
Strikethroughany points that are not applicable.)[ ] Write unit tests for any new features, bug fixes, or other code changes.[ ] Update docs if there are any API changes.[ ] UpdateCHANGELOG.mdwith a short description of any user-facing changes and reference the PR number. Guidelines: https://keepachangelog.com/en/1.1.0/