Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues using fine-grained tokens #227

Open
tpluscode opened this issue Jun 6, 2024 · 0 comments
Open

Issues using fine-grained tokens #227

tpluscode opened this issue Jun 6, 2024 · 0 comments

Comments

@tpluscode
Copy link

I have been trying to use fine-grained PAT to submit a new spec to withfig/autocomplete using the action.

I wanted to use a fork at our org zazuko/autocomplete but when that did not work initially, I created a personal fork at tpluscode/autocomplete

So far, only a classic token worked, which created a PR from the tpluscode form

Trying fine-grained tokens, I would get various errors despite having set it up with the mentioned permissions

HttpError: Resource not accessible by personal access token - https://docs.github.com/rest/branches/branches#sync-a-fork-branch-with-the-upstream-repository

HttpError: Resource not accessible by integration - https://docs.github.com/rest/users/users#get-the-authenticated-user

HttpError: Resource not accessible by personal access token - https://docs.github.com/rest/pulls/pulls#create-a-pull-request

Overall, I think the action is missing a setting to say which is the fork to use. Right now there is way to decide between zazuko/autocomplete and tpluscode/autocomplete, is there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant