-
-
Notifications
You must be signed in to change notification settings - Fork 460
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
Add link to generate access token #1024
Comments
If you are the owner of the repository or it's a public repository then this may be blank. |
I'm hoping to replace this with oAuth soon. At least in the main settings tab. |
As far as I can tell the link is in your Github settings and not specific to any particular repo. Is that correct? Do you need to have different tokens? IE one for the rate limiting and then another for the private repo? |
No, it's user specific.
No, only one token |
In that case, couldn't you remove the multiple access token fields? It's confusing if there's no actual need for it... though I admit I probably just don't understand what's going on. What do the inputs do next to each plugin if you only need 1 access token? Would something like this be easier? And since there's only one link that should be easy enough to put into the description text i think. |
You need the field if you a get an access token from another developer for their private repo. |
Private repos only get designated private after the API call. Sorta a Catch-22. The field is only present until the API response is obtained. If a API response cannot be obtained the the repo is likely private. |
I'm always open to PRs. |
When installing a plugin/theme there's an input for adding the access token:
![image](https://user-images.githubusercontent.com/507025/212999447-4d184532-0a94-45de-a468-3b66de110165.png)
Would be helpful if the description text had a direct link to GitHub so we don't have to go look it up.
Same in the overall settings:
![image](https://user-images.githubusercontent.com/507025/213000275-1c701df5-21a0-4121-96a0-dd2c12400b90.png)
The text was updated successfully, but these errors were encountered: