You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will make a branch which uses the organization secret DOCKERHUB_TOKEN but I do not have access to the credentials currently, so if someone can edit the secret and add a token that would solve it I believe? Otherwise we may have to add a DOCKERHUB_USERNAME secret as well.
In addition, while we are at it we should probably migrate the SNYK_TOKEN there as well
I don't really understand how the other repos do it right now tbh.
github organization secrets are automatically used, so if we add the organization secrets we can just start removing the repo-secrets without any need for code changes.
The issue is that most of these tokens are user-scoped, and hence, using them at the org level is not ideal. I noticed there are plans to add org-scoped token to DockerHub, which would be great. We can keep an eye on that issue.
In the meantime, I will add my personal access token to the org.
Since we are now encountering problems in our CI/CD, it would be good to add a dockerhub token to our organization
I will make a branch which uses the organization secret DOCKERHUB_TOKEN but I do not have access to the credentials currently, so if someone can edit the secret and add a token that would solve it I believe? Otherwise we may have to add a DOCKERHUB_USERNAME secret as well.
In addition, while we are at it we should probably migrate the SNYK_TOKEN there as well
#272
The text was updated successfully, but these errors were encountered: