-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathlesson_3_reflections.txt
More file actions
14 lines (10 loc) · 1.46 KB
/
Copy pathlesson_3_reflections.txt
File metadata and controls
14 lines (10 loc) · 1.46 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
When would you want to use a remote repository rather than keeping all your work local?
In order to allow multiple users to collaborate on the same project or branch Git remote repositories are helpful.
Why might you want to always pull changes manually rather than having Git automatically stay up-to-date with your remote repository?
The remote branch might be considered the stable version of the code and accurate information where my local repository is in development mode. In order to avoid any conflict or bug in my local repository code I'd only pull when necessary.
What is the benefit of having a copy of the last known state of the remote stored locally?
Having a local copy of last known state of remote repository is important so that any new changes that were added in the local copy as well.
How would you collaborate without using Git or GitHub? What would be easier, and what would be harder?
If I do not have access to Git or GitHub I would probably use one of the cloud based sharing files (Box, Dropbox, Google Drive etc...). It would be easier for everyone collaborating to see changes but the hard part would be to be able to merge different code from different people.
When would you want to make changes in a separate branch rather than directly in master? What benefits does each approach have?
In order to reduce impact of the master branch and allow other collaborators to review my code I'd use a different branch to put my changes and do a "Pull Request".