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
Documentation clarification and token usage with dry run #506
Comments
Wow, sorry for the late response @module17 🙈
Yes, we need
Yes, the token is used for all API operations made by this plugin. Maybe you're running into the same issues as here? semantic-release/semantic-release#2053 |
When attempting to run with
dryRun
option, I'm getting a 403 Forbidden when supplying aGL_TOKEN
with onlyread_repository
scope enabled. Documentation states this is the only scope required for a dry run.Adding the
read_api
scope resolves the 403 issue. Is this required?While attempting a dry run, the process repeatedly asks for SSH key passphrase. I would assume the token would be used for all operations. Is this not expected behaviour?
Thanks for looking!
The text was updated successfully, but these errors were encountered: