(README.md) Personal access tokens for public user projects #51
Comments
|
Hey @j1elo thanks for the detailed issue! Do you want to make a PR to update it? Would be happy to make this change. |
|
I wouldn't have enough knowledge about how to work with the GraphQL queries and Github permissions to know how to avoid that the Otherwise, yes I can propose a change to the README. |
digitalronin
added a commit
to ministryofjustice/operations-engineering
that referenced
this issue
Oct 20, 2020
This action was failing with ``` Resource not accessible by integration ``` I think this relates to [this issue](alex-page/github-project-automation-plus#51) so I'm replacing the default, automatically-provided `GITHUB_TOKEN` secret with a personal access token (PAC) belonging to the `cloud-platform-moj github bot account (which I have added to the `operations-engineering` github team). This token has `repo` scope, and has been enabled for MoJ SSO, and added to this repo as the secret `CLOUD_PLATFORM_MOJ_GITHUB_TOKEN` I'm hoping this will enable this action to work as it's supposed to.
nrb
added a commit
to nrb/velero
that referenced
this issue
Dec 9, 2020
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
ashish-amarnath
pushed a commit
to vmware-tanzu/velero
that referenced
this issue
Dec 9, 2020
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
georgettica
pushed a commit
to georgettica/velero
that referenced
this issue
Dec 23, 2020
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
georgettica
pushed a commit
to georgettica/velero
that referenced
this issue
Jan 26, 2021
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
vadasambar
pushed a commit
to vadasambar/velero
that referenced
this issue
Feb 3, 2021
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
|
So is the proper solution to have a token with whole |
|
@D4nte yes so it can access issues and pull requests. Are you having issues with this? |
|
Now fixed. Thanks! |
|
@j1elo I have updated the documentation. Closing this issue for now but please re-open it if anything is missing. |
dharmab
pushed a commit
to dharmab/velero
that referenced
this issue
May 25, 2021
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
ywk253100
pushed a commit
to ywk253100/velero
that referenced
this issue
Jun 29, 2021
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
gyaozhou
pushed a commit
to gyaozhou/velero-read
that referenced
this issue
May 14, 2022
Per alex-page/github-project-automation-plus#51, the `GITHUB_TOKEN` secret doesn't have the appropriate permissions to manage the issue workflows at a repo level. Reverting to the previous secret to get the workflows working again. Signed-off-by: Nolan Brubaker <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The README says that for
the required permission is
repo("Full control of private repositories").However, this permission is actually required also for public repositories and project boards.
I've tested it with a public user-level Project: https://github.com/users/j1elo/projects/1
and a public repository: https://github.com/j1elo/test-repo
secrets.GITHUB_TOKENfails with errorResource not accessible by integration(e.g. https://github.com/j1elo/test-repo/actions/runs/274046708)write:org("Read and write org and team membership, read and write org projects") causes an empty GraphQL response and the errorCould not find the column "..." or project "..."(e.g. https://github.com/j1elo/test-repo/actions/runs/274113617) -- I tried this one just to test if user-level Projects had the same permissions as Organization Projectsreposub-scopes (repo:status,repo_deployment,public_repo,repo:invite,security_events), and it also causes an empty query response.repoallowed the query to find the requested Project.Proposed fix:
Either the README should be updated to reflect that
repois needed also for public user Projects and public repos; or else, if possible at all, the query should be made in a way that doesn't require fullrepopermissions just to search for existing Projects.In any case, thank you very much for this action! :-)
The text was updated successfully, but these errors were encountered: