-
Notifications
You must be signed in to change notification settings - Fork 0
/
lesson_3_reflections.txt
32 lines (21 loc) · 1.57 KB
/
lesson_3_reflections.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
When would you want to use a remote repository rather than keeping all your work
local?
I will not bring my own laptop to every where I go, so it's very convenient to
use a remote repository if I work at other place or other computer.
Why might you want to always pull changes manually rather than having Git
automatically stay up-to-date with your remote repository?
The changes might be from other people or it is not necessary, I still need keep the master version safe and working proprietary.
Describe the differences between forks, clones, and branches. When would you
use one instead of another?
Forks is to copy the commits of other's repository to your Github account. Clones is also to copy the commits of repository, but it could be from Github to local or Github to Github, or local to local. Branches happen in a same repository.
What is the benefit of having a copy of the last known state of the remote
stored locally?
I can work offline, even that I am not ready to merge the files. This allows
me to access it easily.
How would you collaborate without using Git or GitHub? What would be easier,
and what would be harder?
It will be harder to track the previous version and easy to get lost without
using Git or Github.
When would you want to make changes in a separate branch rather than directly in
master? What benefits does each approach have?
To make changes in another branch could prevent to mess up the master version. Using another branch allows us to collaborate with others, get feed back before makes new version works safely and accurately.