-
Notifications
You must be signed in to change notification settings - Fork 43
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
Question: do we really need a Gitlab personal access token for Gitlab ci? #169
Comments
Docs have been updated with an example of using the job token |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currious to understand why this is a requirement for Gitlab because I used the built in gitlab ci release tooling and it doesn't need a token to create a release.
Based on their code they use the
CI_JOB_TOKEN
instead: https://gitlab.com/gitlab-org/release-cliI am not familiar with the inner working of the project yet so I was wondering if this was still a requirement. The
CI_JOB_TOKEN
is a recent addition so I can imagine that maybe it could works as well.The text was updated successfully, but these errors were encountered: