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.
Add support for fine-grained tokens on projects
See original GitHub issueDescription
I added a fine -grained token to my dbt project, I gave it `contents permission
If I update a project or create a new project with this new token, I get the following error
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Introducing fine-grained personal access tokens for GitHub
Fine -grained personal access tokens give developers granular control over the permissions and repository access they grant to a PAT.
Read more >Permissions required for fine-grained personal access tokens
When you create a fine-grained personal access token, you grant it a set of permissions. Permissions define what resources the GitHub App can...
Read more >GitHub Fine-grained Personal Access Tokens - An Introduction
Personal access tokens, or PATS, are an alternative to using passwords for authentication to GitHub when using the GitHub API or the command ......
Read more >GitHub fixes over-broad token permissions with fine-grained ...
Until now, GitHub's personal access tokens could be given restricted permissions, but not per-repository, and only in a few broad categories.
Read more >Finer grained scopes (#351223) · Issues - GitLab
We have a relatively coarse-grained API scope system (api, read_api, read_user). In practical terms, this ends up with many applications and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Is there a way to improve the error message instead of improving the form? Or would that also be high effort?
(e.g. we could detect if the user used
github_pat_and didn’t includeuser:and then could trigger that error message before any github-driven error messages?)🎉 This issue has been resolved in version 0.340.0 🎉
The release is available on:
0.340.0Your semantic-release bot 📦🚀