Skip to content

Clarify scopes required when providing a Git Hub Token #163

@steven-ellis

Description

@steven-ellis

For example the devsecops pattern has a section on

  • Credentials Required in Pattern

This provided minimal guidance on the scopes we should provide when setting up the GitHub token required for the secrets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triaged: waitingIssue reviewed but waiting for author, upstream, third-party etc.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions