question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

(README.md) Personal access tokens for public user projects

See original GitHub issue

The README says that for

Private repository and project board

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

  • Using secrets.GITHUB_TOKEN fails with error Resource not accessible by integration (e.g. https://github.com/j1elo/test-repo/actions/runs/274046708)
  • Using write:org (“Read and write org and team membership, read and write org projects”) causes an empty GraphQL response and the error Could 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 Projects
  • At this point, I tried using all of the repo sub-scopes (repo:status, repo_deployment, public_repo, repo:invite, security_events), and it also causes an empty query response.
  • Finally, using the whole repo allowed the query to find the requested Project.

Proposed fix:

Either the README should be updated to reflect that repo is 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 full repo permissions just to search for existing Projects.

In any case, thank you very much for this action! 😃

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:5
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
D4ntecommented, Apr 29, 2021

Now fixed. Thanks!

1reaction
D4ntecommented, Apr 28, 2021

So is the proper solution to have a token with whole repo permission?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Introducing fine-grained personal access tokens for GitHub
PATs are an easy way to mint tokens that can be used to call the GitHub API and establish git connections over HTTPs....
Read more >
Managing Composer Github access with Personal Access ...
Step 1: Create a personal access token ... Go to https://github.com/settings/tokens and generate a new token. ... You will need to specify all...
Read more >
How to Use GitHub Personal Access Tokens - ITPro Today
How to Use GitHub Personal Access Tokens · 1. Click your portfolio button on any page in GitHub, then press the Settings button....
Read more >
Project access tokens - GitLab Documentation
Create a project access token · On the top bar, select Main menu > Projects and find your project. · On the left...
Read more >
How to Create a Repo-scoped Github Access Token in an ...
Since this Github action is for an Organization Account, you'll need to allow it to be installed on "Any Account". That makes the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found