Describe the bug
When using a new fine grained PAT, not all settings are accessible depending on the scope and permissions granted...
To Reproduce
Have not determined full extent of this issue and how to reproduce yet, still developing understanding of the issue.
Expected behavior
Action works as it has in past.
Screenshots
Not yet available
Additional context
GitHub enabled new Fine Grained PAT, and when I was initially testing with these new types of PATs, I got a lot of errors until I reverted to the old type. It also seems that the OAUTH scope of the new PAT types do not provide any info when queried with repo._requester.oauth_scopes like the old ones did.
Describe the bug When using a new fine grained PAT, not all settings are accessible depending on the scope and permissions granted...
To Reproduce Have not determined full extent of this issue and how to reproduce yet, still developing understanding of the issue.
Expected behavior Action works as it has in past.
Screenshots Not yet available
Additional context GitHub enabled new Fine Grained PAT, and when I was initially testing with these new types of PATs, I got a lot of errors until I reverted to the old type. It also seems that the OAUTH scope of the new PAT types do not provide any info when queried with repo._requester.oauth_scopes like the old ones did.