Skip to content

Documentation clarification and token usage with dry run #506

Open
@module17

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!

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions