semantic-release / semantic-release/gitlab
Documentation clarification and token usage with dry run
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 344
- Forks
- 89
- Avg merge
- 16h 11m
- Merged PRs (30d)
- 4
Description
When attempting to run with dryRun option, I'm getting a 403 Forbidden when supplying a GL_TOKEN with only read_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!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current documentation for dry-run authentication, GL_TOKEN scopes, and SSH key usage, then reproduce the reported behavior with only read_repository and with read_api enabled. Done means the documentation accurately states the required scope and whether repeated SSH passphrase prompts are expected.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100