Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update Readme.md to remove ambiguity for personal token creation #445

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Readme.md to remove ambiguity for personal token creation #445

wants to merge 1 commit into from

Commits on Apr 6, 2023

  1. Update Readme.md to remove ambiguity for personal token creation 

    There has been recent change in the ways to create GitHub API token. Earlier there was only one option to create token but now with the recent change one more option is added i.e. Generate new token (Fine-grained, repo-scoped). 
The current documentation assumes we are creating a token with earlier option i.e. Generate new token (For general use) and thus says "You'll need a GitHub API Token with repo and user scope...". With the advent of new option this is invalid. 
Hence we need to specify in the Readme.md file to create the token using previous option only.
This commit updates that.
    @DhruvAwasthi
    DhruvAwasthi committed Apr 6, 2023
    Configuration menu
    Copy the full SHA
    1b511d8 View commit details
    Browse the repository at this point in the history