That might be not so easy to solve so i strongly recommend you to stash your changes before doing 'pull'. By the way, make sure to have Git installed as I'm using Git Credential Manager. This time, for some weird reason, it's going to remember your credentials. Sourcetree is going to ask you for GitHub credentials. If you didn't stashed, you will probably get conflicts now, because the system is not smart enough to know whats the priority: what you have changed or what people from other branches changed. Create a repository on GitHub account then clone it with Sourcetree via HTTPS. In the scope, check ‘repo’ for full control of private. Pull things people updated on your head branch using git pull origin branchName In page, Go to Settings -> Developer Settings -> Personal Access Token, click ‘Generate new token’ Click ‘Generate new token’ 2. Reseting your commits, but keeping the changes by using git reset -soft HEAD^ People probably have made updates into the project you've cloned (that explains the commits behind) and you've also made commits since you've cloned, and didn't pushed yet (and that explains the commits ahead). Create a repository on GitHub account then clone it with Sourcetree via HTTPS.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |