chore(ci): use explicit secrets where possible#3042
Open
gforsyth wants to merge 1 commit into
Open
Conversation
gforsyth
added
improvement
gforsyth
commented
May 27, 2026
| @@ -1,5 +1,4 @@ | |||
| name: build | |||
|
|
|||
Contributor
Author
There was a problem hiding this comment.
The whitespace changes are a result of using yq to bulk-edit the workflow files. The loss of the whitespace isn't my first choice, but I think it's a reasonable trade-off for what yq allows us to do, especially when making bulk edits across repositories.
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.
Followup to #3009 -- some of the secret handling was added in later PRs. Adding it in to
raftnow.This is also part of rapidsai/build-planning#275