Search…
Using a GitHub Personal Access Token
By default, GitHub prevents third-party applications from automatically creating API tokens for organizations. This can mean that even though you've authenticated Graphite with your GitHub account, we may not be able to generate the token needed to let you create, view, or update your pull requests (if your org has not changed this setting).
For cases such as this one, where you want to give command line tools and APIs limited access to work with your account, GitHub recommends that you create and use Personal Access Tokens which do have the necessary permissions.
To use a Personal Access Token with Graphite:
  1. 1.
    Generate a new token from your token settings page on GitHub with the following permissions:
    • repo (for the repo you want to work in)
    • read:org
    • read:user
    • user:email
  2. 2.
    [If your org has SSO] Check the token settings page on GitHub and make sure you enable SSO for the Personal Access Token you're using with Graphite.
  3. 3.
    Next, add your new token to Graphite via the Graphite web dashboard settings page.
Here's what your GitHub Personal Access Token settings page should look like when properly set up to use with Graphite
Once your token is added, you should be able to do the following:
  • Select your repo from the drop-downs in each section of the Graphite web dashboard
  • Run gt stack submit in the Graphite CLI to create pull requests in GitHub for every branch in your stack
If this still doesn't resolve your issue, please ping us on Slack so we can troubleshoot!
Slack
Export as PDF
Copy link