Remote Collaboration Overview
In a typical remote collaboration, you need to seamlessly work on both your local computer (i.e., the command line and a text editor) and a Remote Repository on the GitHub website.
The following is one of the typical flows of remote collaboration on Git & GitHub.
A typical cycle of remote collaboration
- Developer A (a project leader and the owner of the Remote Repository) establishes a link between his Local Repository and the Remote Repository used for the project. To establish the connection, he runs the
git remotecommand. - Once Developer A's Local Repository is linked with the Remote Repository, he can push his project directory to the Remote Repository by running the
git pushcommand. He also gives Developer B access to the repository at this point. - After Developer B obtains access to the Remote Repository, she can bring the project directory from the repository by running the
git clonecommand. Thegit clonecommand establishes a link between the Remote Repository and her Local Repository, and the command also creates a copy of the project directory on her local computer. - There are two approaches for getting the project files from the Remote Repository the second time:
- Running the
Subscribe now for
uninterrupted access.