Using a Fine-Grained PAT

[santaimpersonator]

Has anyone tried implementing the new, fine-grained personal access token in their workflow?

• Currently, the classic token works for us.
• However, we'd like to implement the fine-grained token to limit its privledges to read-only.

---

I noticed when setting up the token with our bot account, it wasn't able to access the mkdocs-material-insiders repo under the Repository access section.

• I tried enabling the expected privledges and making them read/write.
  
  
  However, this is the error message we get

  remote: Write access to repository not granted.
  fatal: unable to access 'https://github.com/squidfunk/mkdocs-material-insiders.git/': The requested URL returned error: 403

My guess is that the insiders repo would have to be under an organization and the bot account would have to be part of the organization to be able to select the appropriate Resource owner and specific Repository access.

[squidfunk]

We'll be moving the Insiders repository under an organization in the coming weeks/months. We can't just do that instantly, because there are hundreds of collaborators on that repository, so we need to think of a good migration path. When we started the Insiders program, it wasn't clear whether it would be a success, which is why we just started by going with a private user-level repo 😉

[santaimpersonator]

Oh, awesome... that is great news!