Push and crawl in GitHub fork projects

GitHub-Fork Submit project: Your own warehouse and the original repository for GIT synchronization operations. 1. Get updated new code for your fork's original repository, or increase if no remote Origin branch is available. git remote add upstream [email protected]:P Arrotsdl/parrots.git
git fetch upstream2. Switch to your local master branch and merge the latest Upstream/master code into your local master git checkout mastergit merge Upstream/master at this point, Your local library is already fully synchronized with the original repository. Note, however, that at this point the local repository on your computer is synchronized with the remote GitHub repository, and your own github repository is not synchronized, and you need to use the git push command to submit your local repository to GitHub.

Git push Origin Master

Generally in the team of multi-person development mode is this:

• First, you can try to push your own changes with GIT push origin branch-name

• If the push fails, because the remote branch is newer than your local, you need to first try to merge with Git pull

• If there are conflicts in the merge, resolve the conflicts and submit them locally

• No conflict or conflict resolution, then GIT push origin branch-name push to succeed

If Git pull hints "No tracking information", then the link relationship between the local branch and the remote branch is not created, with the command git branch--set-upstream branch-name origin/ Branch-name.

Branch Push and merge in multi-person collaboration

Push and crawl in GitHub fork projects