-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlesson_3_reflections.txt
46 lines (35 loc) · 2.2 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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
QUESTION: When would you want to use a remote repository rather than keeping all your work local?
ANSWER: In order to collaborate with others remotely.
-----------------------------------------------------------------------------
QUESTION: Why might you want to always pull changes manually rather than
having Git automatically stay up-to-date with your remote repository?
ANSWER: In the event that you want to reverse any changes committed
on the remote repository.
-----------------------------------------------------------------------------
QUESTION: Describe the differences between forks, clones, and branches.
When would you use one instead of another?
ANSWER: Forks are used to clone a project on GitHub. Clones are used
to copy a repository on a local machine. Branches are used to branch
away from another repository.
-----------------------------------------------------------------------------
QUESTION: What is the benefit of having a copy of the last known state of
the remote stored locally?
ANSWERED: If you are working offline then you can check the remote
repository state without having to go online.
-----------------------------------------------------------------------------
QUESTION: How would you collaborate without using Git or GitHub? What
would be easier, and what would be harder?
ANSWER: I would use a file sharing service like Google Drive or Drop Box.
Usin Git and GitHub would be easier because of being able to manage
changes to files and Git provides version control. Google Drive and Drop
Box may provide some thing similar but there is not staging area and way
to easily collaborate.
---------------------------------------------------------------------------
QUESTION: When would you want to make changes in a separate branch rather
than directly in master? What benefits does each approach have?
ANSWER: When you are testing out a new feature that you are not sure you
want to include in your project. Working in the master without branching
has the benefit of easily having those changes already in the master
without having to merge. The benefit of branching and the making the
changes has the benefit of keeping the master in a stable condition
and not affect by a bunch of changes.