Switch to fine-grained PAT

[itrich]

GitHub introduced fine-grained PAT to allow better control of access rules to the GitHub API: https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/

This will allow us to issue an organization PAT without the hassle to create an individual PAT for every owner of our organization.

However, the new fine-grained PAT still don't support GraphQL (which is used by https://github.com/opentelekomcloud/ansible-collection-gitcontrol), so we need to wait until this issue will be closed: https://github.com/github/roadmap/issues/622

[itrich]

/remind-me 2023-03-01 Have a look at GraphQL support for fine-grained PAT

[octo-reminder[bot]]

⏰ Reminder Wednesday, March 1, 2023 9:00 AM (GMT+01:00)

Have a look at GraphQL support for fine-grained PAT

[octo-reminder[bot]]

🔔 @itrich

Have a look at GraphQL support for fine-grained PAT

[itrich]

/remind-me 2023-04-01 Have a look at GraphQL support for fine-grained PAT

[octo-reminder[bot]]

⏰ Reminder Saturday, April 1, 2023 9:00 AM (GMT+02:00)

Have a look at GraphQL support for fine-grained PAT

[itrich]

Fine-grained PAT still don't support GraphQL, so we need to stick to classic PAT. As I'll be leaving the team, there should be at least one more owner (besides @maxwolfs) that has a valid PAT configured here in the repository's secrets.

@jschoone @fkr @garloff: Who of you will jump in?

[fkr]

I jumped in. Thanks @itrich for your n00b support.

[garloff]

I guess someone would need to explain to me what PAT is (protection access table?) and why GraphQL would be relevant here. Thanks @fkr to jump in, so I don't need to understand.

[octo-reminder[bot]]

🔔 @itrich

Have a look at GraphQL support for fine-grained PAT