![]() That’s it! From here, you’ll be able to push workflow changes from your SourceTree client. This will redirect to a web page login on GitHub. 2.Settings -> Developer Settings -> Personal access tokensGenerate new tokentoken. Select the token tab, and paste in the PAT created in the steps above.Īlternatively, if the repos that you’re working with exist under an organisation that enforces OAuth authentication, click the Sign in with your browser button. It should pop-up with something like this: The git client will detect that there are no credentials cached and will hand-off control to the Git Credential Manager. Then from the SourceTree terminal window, push to any repo. With a fresh PAT created, head back into SourceTree: Tools -> Options -> Authentication and remove all the GitHub credentials. Next, on the GitHub web page navigate to the Profile menu, click settings and from the ‘Developer Settings’ section, create a new Personal Access Token (PAT). To verify that it is connected to the remote on GitHub, click the "Settings" gear in the top right-hand corner and you should see the GitHub remote in the "Remotes" section.Git config -system credential.helper manager-core Once that's done, you can double click the new bookmark and use SourceTree as you normally would. You can either clone it to a new location, or add the directory manually in the Local tab. Then in SourceTree Tools -> Options -> Authentication and delete the accounts as others have said. You can revoke a PAT at any time, for various reasons. Regenerated the token in github (Your Profile -> Settings -> Security then find a link saying Personal Access Tokens) (dont forget to tick the appropriate boxes to grant permissions). Edit the token name, token expiration, or the scope of access thats associated with the token, and then select Save. Select the token you want to modify, and then Edit. Since this was just a test repo, I'll move it to the trash.)Īdding an Existing Repo that Has a Corresponding Remote to SourceTreeįor some reason if you click "Clone" next to a repo you already have on your local machine and select the existing directory, it won't connect the remote repo with your existing copy. Under Security, select Personal access tokens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |