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 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.
I 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:
You don't need to provide a PAT but there are some restrictions, The only one I can recall off the top of my head is that we required the GIT_STRATEGY to be clone so that we can access the commits without the API.
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: