chore(COD-4237): remove the hard-coded --secret option #216
Conversation
This file contains 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
jeremydubreil
force-pushed
the
remove-secret-option
branch
from
fc38260 to
f40f2f3
Compare
jeremydubreil
commented
Jan 29, 2025
| @@ -60,7 +59,6 @@ async function runAnalysis() { | |||
| 'ci', | |||
| '--keyring', | |||
| trustedKeys, | |||
| '--secret', | |||
There was a problem hiding this comment.
This is the only line changed by the PR. The rest is pre-existing auto-formatting issues.
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.
There is no reason for the
--secretto be hard-coded in the GitHub Actions code. This means the option can never be disabled since CLI options have the highest priority.