Skip to content

πŸ“ Documentation: Exactly which granular token permissions are necessary?Β #925

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Bug Report Checklist

Overview

Right now, the docs generally phrase the GitHub Personal Access Token ("PAT") required for the repository's ACCESS_TOKEN secret as needing "repo and workflow permissions". That terminology adheres to the classic PATs that I've been using.

But, GitHub now has "fine-grained" PAT support in beta. The docs should mention exactly which fine-grained token permissions are necessary (if they actually work in this template yet).

Additional Info

Mentioned by @KATT as working in https://github.com/KATT/tupleson, I hope.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions