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
One for storing configuration only, and the other one for all the GitHub Actions responsible for applying the configuration changes.
Hopefully, then we would be able to give out access to the first one more freely while still protecting the secrets well enough in the second one.
It's a follow up to #58 (comment)
The idea was originally proposed in ipfs/github-mgmt#30 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
One for storing configuration only, and the other one for all the GitHub Actions responsible for applying the configuration changes.
Hopefully, then we would be able to give out access to the first one more freely while still protecting the secrets well enough in the second one.
It's a follow up to #58 (comment)
The idea was originally proposed in ipfs/github-mgmt#30 (comment)
The text was updated successfully, but these errors were encountered: