So, for your local copy, the actual repository is upstream. Whenever you clone a git repository, you get a local copy in your system. Let’s take a look at different types of git upstreams. For example, when you clone from Github, the remote Github repo is upstream for the cloned local copy. In the git world, upstream refers to the original repo or a branch. Like the literal meaning, upstream refers to something which points to where it originated from. Note: We are following the name “main” instead of “master” considering the removal of terms like “master” and “slave” in the IT community. Have you wondered how to keep the forked repo in sync with the main repo? It’s done by adding the main repo as the upstream. You will also learn about different scenarios where git upstream is used and how to apply it in your git development workflow. Last but not least, you can find me on Twitter.In this blog, you will learn everything about setting up an upstream for a git repository, a branch and the -set-upstream-to command usage Now you have the branch on your local repo, and you can test it out locally! □ Running this command will automatically create a branch with the same name in our local repo. You will see in the command line that we have fetched the branches on the upstream repo, including the target branch. git remote -vįetch data from the upstream. We can copy this link by going to the repo on GitHub, clicking the green button with "Code" written on it, and copying the HTTPS link.Ĭheck if the new upstream has now been added. Original-repo-url is the HTTPS URL of the repo that we fork. If we haven't configured a remote that points to the upstream repo, we will get: origin (fetch)Īdd a new remote upstream repo that will be synced with the origin repo. So, I hope you can gain something too from our journey! □ Fetch a branch from the upstream repoĬheck our current configured remote repo for our fork. However, we learned a lot from this accident. In this case, I am the maintainer, and my teammate is the contributor. We found out later that what we're doing is an open-source workflow, where we maintain and contribute to a repo. My teammate and I started this project with one of us creating a repo and the other forking the repo.īut for collaborating, we could do it differently, which I will cover in another blog post. So, we need to set the origin repo to point to the upstream repo. He then forked this repo, which automatically becomes his origin repo.įor him to fetch a branch - that hasn't been merged to main - from the upstream repo, his origin repo should have access to the upstream. Then we tried to step back and figure things out.įrom my teammate's side, my repo is the upstream repo. We mostly got the error of fatal: couldn't find remote ref. I asked my teammate to fetch this branch and test things out locally before merging it into the main branch.Īfter making sure that we didn't have anything to fetch and merge from the remote repo, and after several attempts, we still couldn't fetch the branch from the remote repo. Then I pushed this branch to the remote repo and created a pull request. Recently, I created a branch to make some changes. I created a repo for the project, and my teammate forked this repo. I am collaborating with a friend to create a project in React.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |