-
Notifications
You must be signed in to change notification settings - Fork 0
/
lesson_3_reflection.txt
39 lines (28 loc) · 1.57 KB
/
lesson_3_reflection.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
When would you want to use a remote repository rather than keeping all your work
local?
it's a backup in case of disk failure
it also allows for synchronisation between different computer
Why might you want to always pull changes manually rather than having Git
automatically stay up-to-date with your remote repository?
to have control.
Describe the differences between forks, clones, and branches. When would you
use one instead of another?
fork is like a clone on github, but github tracks the original repo
a clone allows to sync the same repo on different location
for exemple a branch allows to develop new features of the code without
breaking your code
What is the benefit of having a copy of the last known state of the remote
stored locally?
it might be useful to fix conflict. For exemple, if someone else changed
the remote directory and that those changes are not compatible with your
work
How would you collaborate without using Git or GitHub? What would be easier,
and what would be harder?
i would probably send email with files in it... it would be possible to
make minor fixes to one file at a time but it would be impossible to keep
track of complex changes.
When would you want to make changes in a separate branch rather than directly in
master? What benefits does each approach have?
you should make a new branch for each new feature of each bug fix, especially
when you are collaborating on a project. If you are alone and you work on a
single subject at a time, you might do everything on your master...