#20282 Release process: underdocumented Github access token Issue created by tgolsson Describe the bug This page: https://www.pantsbuild.org/docs/release-process, currently says to use a GitHub PAT for some steps. This seems to primarily be step 1, in order to create PRs. However, it doesn't mention what kind or what permissions are needed, and I wasn't able to find a working configuration. Either I'd get a 403 forbidden (with classic token), or a 422 with the detail

Resource not accessible by personal access token

for a fine-grained token. I gave all permissions I deemed necessary to create PRs -- issues, PRs, repository, user. When I tried creating a modern fine-grained token I wasn't able to grant permissions on

pantsbuild/pants

, which might be an interesting factor -- but a PR from my fork should still work. Either way, it might be nicer to use the

gh

cli tool everywhere, since it already solves most of these issues. Pants version Saw the same issue on 2.19 and main. OS Linux pantsbuild/pants