Remote Repositories - Concepts Flashcards
T/F: You can merge history between two different copies of a repository much in the same way you would merge history between two branches in the same repository.
True
T/F: It’s considered bad form to use a “central” remote repository to help organize your project workflow; no one does this because it circumvents the advantages of Git’s decentralized architecture.
False
The act of sending changes to and from remote repositories in Git is typically described by what verbs?
- push and pull
What is a sensible reason to make use of a remote repository?
- you intend to work on the project with a team of other contributors
- you’d like a remote copy of your project history in case something happens to the repository on your computer
- you’d like to have an authoritative , “central” version of the project you’re working on, and a remote repository on a neutral server servers that purpose
In Git, the act of creating a new repository that is a copy of another one is called _____
- cloning
T/F: Repository hosting services often provide analysis and statistics that aren’t easy to find in a raw git repository.
True
Cloning a GitHub repository to your own account is done through a process called _____
- forking
T/F: One advantage of repository hosting services like GitHub is that they expose your public projects to the broader software development community.
True
What’s the helpful aspect of a tool like Pull Requests that isn’t present in git by default?
- being able to discuss changes right alongside the commits that include those changes
You don’t need to use a third-party service to host your remote repositories, but doing so can provide you with the following benefits:
- social features, an easy-to-read interface for your project history, and project management tools
