We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Given GitHub CLI is present and the user is authenticated. The nuke :secrets command could set the secret variable directly in GitHub.
nuke :secrets
gh auth status
gh secret set <secret-name> --org <organization> --repos <repo-name>
gh secret list --org <organization> --repo <repo-name>
See https://nuke.build/docs/global-tool/secrets/
No response
The text was updated successfully, but these errors were encountered:
Ok, I would like to tagle this one. But I got questions :D Where should I ask them?
Sorry, something went wrong.
@matkoch is this still relevant?
No branches or pull requests
Description
Given GitHub CLI is present and the user is authenticated. The
nuke :secrets
command could set the secret variable directly in GitHub.Usage Example
See https://nuke.build/docs/global-tool/secrets/
Alternative
No response
The text was updated successfully, but these errors were encountered: