-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e8fcc73
commit e1929c9
Showing
1 changed file
with
11 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,16 @@ | ||
When would you want to use a remote repository rather than keeping all your work local? | ||
Not sure why you even need to use remote instead of local. | ||
Q: When would you want to use a remote repository rather than keeping all your work local? | ||
A: Not sure why you even need to use remote instead of local. | ||
|
||
Why might you want to always pull changes manually rather than having Git automatically stay up-to-date with your remote repository? | ||
Sounds like automatic pull is not a good idea, because it doesn't allow you to control what changes are pulled and when. It's better | ||
Q: Why might you want to always pull changes manually rather than having Git automatically stay up-to-date with your remote repository? | ||
A: Sounds like automatic pull is not a good idea, because it doesn't allow you to control what changes are pulled and when. It's better | ||
To pull manually, so you update you local files when you are ready | ||
|
||
|
||
Describe the differences between forks, clones, and branches. When would you use one instead of another? | ||
Fork is a copy of the repository in the Github, this copy a sits own master branch and is like another repository. Any changes to it don't affect original repository and cannot be pushed there | ||
Q: Describe the differences between forks, clones, and branches. When would you use one instead of another? | ||
A: Fork is a copy of the repository in the Github, this copy a sits own master branch and is like another repository. Any changes to it don't affect original repository and cannot be pushed there | ||
Clone is a copy of repository as well, but it's purpose is to make changes to the original repository when they pushed. It is a copy from GitHub to local machine mainly | ||
Branch is a special copy of the repository, which has a label, called branch name. There can be many of those within one repo and they can be merged together and pushed. These changes will affect the repository. | ||
Branch is a special copy of the repository, which has a label, called branch name. There can be many of those within one repo and they can be merged together and pushed. These changes will affect the repository. | ||
|
||
Q: What is the benefit of having a copy of the last known state of the remote stored locally? | ||
A: The benefit is that you are able to track what changes were made by other team members while you were making yours. This will also give you opportunity to | ||
Compare changes and merge if necessary |