-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Make GITHUB_TOKEN optional for local development? #266
Comments
Wow, I never set GITHUB_TOKEN. I just |
I guess it's because I don't ever rebuild those, and I guess that must not be required. |
It would be a fine addition, thanks! |
You have this cached in
When I cleared my
|
My first time up on a new machine I also got this:
And it also seems to hang forever there. |
I imagine I had a .env on other machine that I wasn't aware of. Note that it seems to work with a no-scope-no-privileges token (I don't think it needs the privs currently stated in the README) |
Created draft #268 |
Ah interesting! Briefly wondered why these are needed when you are someone with no privs for github.com/ddev in the first place |
no-scope-no-privileges does not work
Your token has not been granted the required scopes to execute this query. The 'login' field requires one of the following scopes: ['read:org'], but your token has only been granted the: [''] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.
- Your token has not been granted the required scopes to execute this query. The 'url' field requires one of the following scopes: ['read:org'], but your token has only been granted the: [''] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.
- Your token has not been granted the required scopes to execute this query. The 'avatarUrl' field requires one of the following scopes: ['read:org'], but your token has only been granted the: [''] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.
- Your token has not been granted the required scopes to execute this query. The 'login' field requires one of the following scopes: ['read:org'], but your token has only been granted the: [''] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.
- Your token has not been granted the required scopes to execute this query. The 'url' field requires one of the following scopes: ['read:org'], but your token has only been granted the: [''] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.
- Your token has not been granted the required scopes to execute this query. The 'avatarUrl' field requires one of the following scopes: ['read:org'], but your token has only been granted the: [''] scopes. Please modify your token's scopes at: https://github.com/settings/tokens. I'm an "outside collaborator on 1 repository" for ddev organization, so a test with someone not added to ddev org would be helpful. |
I have a GitHub account without DDEV access, and confirm that |
This was fixed in Thanks! |
In my personal opinion it is a bit of a challenge that people who want to add a blog article PR need to setup a GitHub key first.
They also might not understand why they have to do it on their own account. An information what the key does is also missing in README.md
And ... first it works without a token, but then you run into the GitHub API rate limit errors when you try
ddev npm run build
.My proposal would be something like this for
api.ts
:If there is not
GITHUB_TOKEN
, we simply don't render sponsors, contributors, latest releases.We might add a warning if this is a production build and the
GITHUB_TOKEN
is still missing.(Goal: Make it as easy as possible to contribute, guess adding blog articles via Gitpod would also be great)
The text was updated successfully, but these errors were encountered: