You tell your local Git to clone that repository onto your local computer. Well, it’s easy if you are starting with a situation where the repo you want to use is already stored on GitHub. So you are likely to want a Git repository to live both on your computer and at GitHub.
This is good for tasks such as backup (keeping a copy of your work offsite, in case something happens to your computer) and collaboration (because multiple people might be allowed to copy the same remote repository onto their computer and work on it).Ī common place to keep the remote copy of a Git repository is GitHub.
One of Git’s most important features is its ability to synchronize between two copies of a repository living in two different places - typically, a local copy living on your computer, and a remote copy living somewhere off on the Internet. (You might want to read the earlier post first, before reading this one, so that we’re sharing the same conceptions of what Git is and how it works.) That syncing feeling This change, judging by the number of posts and questions about it online, seems to worry a lot of users but as we shall see, it’s really not a big deal at all.
It’s the story of a change in the policies, at GitHub and within Git itself, about what the default initial branch name should be. Today’s article is about the branch names master and main. Following on from my earlier blog post on understanding (and misunderstanding) Git, let’s dive deeper into some individual Git topics.
0 kommentar(er)
