You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Guidance on permissions for fine-grained tokens #365
yes, did something change about permissions for tokens? I remember it being a checklist with code-like names as described in the documentation (org:read) but in the Github UI they’re all English-y names now
Following up, I found that these permissions are what worked:
I didn’t iterate this one step at a time because I needed someone to approve permissions changes for me, but this is probably the minimal set, or close to it, for our structure, at least.
Activity
eilidhmae commentedon Jan 24, 2025
Second this. I am blocked, and find this step too vague to proceed.
backspace commentedon Oct 30, 2025
yes, did something change about permissions for tokens? I remember it being a checklist with code-like names as described in the documentation (
org:read) but in the Github UI they’re all English-y names nowbackspace commentedon Oct 30, 2025
Following up, I found that these permissions are what worked:
I didn’t iterate this one step at a time because I needed someone to approve permissions changes for me, but this is probably the minimal set, or close to it, for our structure, at least.
KevinWu098 commentedon Jan 5, 2026
Implemented PAT on an org recently. Based on this comment in a similar thread, I was able to get it working. My settings being:
Actions: Read/Write
Contents: Read/Write
Metadata: Read (required)
Happy to put up a PR to add this guidance to the docs, lmk @peter-evans