-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlesson_3_reflection_prompts.txt
41 lines (28 loc) · 1.64 KB
/
lesson_3_reflection_prompts.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
When would you want to use a remote repository rather than keeping all your work
local?
- When there are more than 1 person working on the same project
- To share code among different computers
Why might you want to always pull changes manually rather than having Git
automatically stay up-to-date with your remote repository?
We won't want to update our files if we in the middle of a logical change
Describe the differences between forks, clones, and branches. When would you
use one instead of another?
Forks
- copying an existing GitHub repository into own GitHub repository.
- When you would like to change some code in an existing github repo to suit your own need
Clones
- copying an existing repository into own repository (local copy)
- When you would like to change some code in an existing repo to suit your own need
Branches
- copying existing files from same repository
- when you wish to temporary work on some big changes and planning to merge the changes back to master later on
What is the benefit of having a copy of the last known state of the remote
stored locally?
To allow us to work offline and merge with remote once it's ready
How would you collaborate without using Git or GitHub? What would be easier,
and what would be harder?
Copy and paste codes manually. Much harder
When would you want to make changes in a separate branch rather than directly in
master? What benefits does each approach have?
Branch is useful when we wanna make huge changes and wish not to affect existing code until it is complete.
Working on master branch still necessary if we are only making smaller changes / bug fixes