The difference really comes down to concept, as well as the personal preference to manually manage account credentials. Both are tied to the user who requests the token, meaning they will have the same permissions as the user. Personal access tokens and OAuth tokens look very similar and serve the same purpose. But if you want to dig a little bit further into this change, we invite you to read on… Now, if you just needed to establish or verify your GitHub connection, your work here is done. Make sure you check the connection for each profile to avoid surprises when GitHub enforces this change.įor more information and further details about GitKraken’s GitHub integration, please see our Support documentation. Reminder: GitKraken allows for multiple profiles, each with its own settings and preferences. If successful, the next screen should say: “GitHub and GitKraken are good to go!” □ Follow the process on the GitHub login page to log into your GitHub account.In the new web browser window that opens, click on “Continue authorization”.If you are not already connected it will look like this: Click on GitHub to reveal your connection status.If you have already connected previously, your status will show “Connected” and there is no further action needed.Open the Preferences menu (using the gear ⚙️ icon in the upper right), and click on Integrations from the left-hand menu.To connect to GitHub via OAuth, or to double-check that you’ve already done: Connecting GitKraken to GitHub with OAuth
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |