Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Question: do we really need a Gitlab personal access token for Gitlab ci? #169

Open
xNok opened this issue Jan 12, 2024 · 2 comments · May be fixed by #170
Open

Question: do we really need a Gitlab personal access token for Gitlab ci? #169

xNok opened this issue Jan 12, 2024 · 2 comments · May be fixed by #170

Comments

@xNok
Copy link

xNok commented Jan 12, 2024

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-cli

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.
@cliedeman
Copy link
Contributor

cliedeman commented Jan 14, 2024 •
edited

Hi @xNok

Looks like the docs are a little outdated: #141

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.

@cliedeman cliedeman linked a pull request Jan 14, 2024 that will close this issue
Open
@dannylongeuay dannylongeuay mentioned this issue May 3, 2024
Merged
@dannylongeuay
Copy link
Contributor

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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update gitlab token docs go-semantic-release/semantic-release
3 participants
@cliedeman @xNok @dannylongeuay