![]() Hope this makes sense, happy to have a more involved discusssion if necessary. call is also important because in our case, the reference repositories for agents running on k8s are on an NFS share, but the volume gets mounted read-only so attempting to add the remote will always fail because git needs write access to be able to lock the repository's config file. branch at the same time with: git push -set-upstream origin new-branch. bit from the initial discarded implementation of reference repositories for submodules and looking at it now with more experience/context, it seems like that code was attempting to add a remote for the submodule's repository to the main repository's mirror, which is not the same situation we have now. with: git checkout -b new-branch and then when we make changes and commit them. These can be linked with branches on the remote, or they could exist with no remote counterpart. Each one has a specific purpose and use case, and mastering them will make it easier for. Local working branches When you run git branch -all, you will also see the local working branches. In summary, when working with remote repositories, it's important to understand the basics of adding and modifying remote repositories, as well as the commands and concepts of git push, git pull, git fetch, git merge and branching, forks and pull requests. Pretty sure I cargo-culted the remote add. This is safe to do if you are using GitHub, because branches merged via pull requests can be restored. Git is a popular and widely used version control system. ![]() This Is Why Darius Foroux Save 20 Hours a Week By Removing These 4 Useless Things In Your Life Jacob Bennett in Level Up Coding Use. ![]() I don't think that additional submodule-1 remote is ever going to get used. JavaScript in Plain English Coding Won’t Exist In 5 Years. url = +refs/heads/*:refs/remotes/submodule-1/*
0 Comments
Leave a Reply. |