![]() If you want to continue working only by yourself for the remaining part of the project/feature, then you can create a new branch from your co-worker’s branch. Your co-worker will be able to pull your changes. You can add your code changes and push them. Now, you will get all the recent changes made on your co-worker’s forked repo branch. You can add your code changed and push it and your team member can pull it in his/her local setup. In such a case, you can pull your team member’s fork branch and continue working on whatever is done in that team member’s branch. ![]() There can be a scenario where you would need to continue working on the work done by someone else on your team. This will also set up a tracking relationship between the local branch and the remote branch(upstream).Facebook Tweet LinkedIn Pin Print Email Shares By doing this we will be able to view the changes made by others and also modify them. We can check out a remote branch by first fetching it to our local repository and then creating a new local branch based on it. Collaborators will often share branches by pushing them to the remote repository. We can also see that our local branch feature has an upstream origin/feature by running the Git Branch command with the -vv flag.īranches are a great way to work on features and try out new things. ![]() Let's go back to our master branch and run the Git Checkout command with the -track option to create a new local branch based on the remote-tracking branch.But we can view the commit history by using the Git Log command. As shown below, our HEAD gets detached and we cannot make new changes without creating a new branch. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |