-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
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
Create release environments #56
Labels
distribution
Distribution of the binaries
Comments
@dex4er fyi |
@dex4er I assigned this issue also to you cause now you can create the other needed envs and contact me if needed. |
Now it is urgent as the release is almost prepared. @robertobandini please prepare the "signing" environment with the secrets the same as on nightly. |
@dex4er I prepared a new environment here called "signing", can you try it? Thanks! |
Implemented and already used. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Long story short: it seems that the best way to protect secrets ecc for example to do signign/publish ecc is to use a specific environment with its own secrets and require approval by a reviewer.
So, I think actually I'll create the envs needed and mark myself as the approver, so when we have a new release, for example, I'll approve the job using that specific env with specific secrets.
The text was updated successfully, but these errors were encountered: