-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlesson_3_reflections
29 lines (18 loc) · 1.77 KB
/
lesson_3_reflections
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
When would you want to use a remote repository rather than keeping all your work
local?
GitHub is easy to use. Using a remote is a great idea because I don't really has to keep local copies on my machine.
Why might you want to always pull changes manually rather than having Git
automatically stay up-to-date with your remote repository?
I can make changes and commit them on GitHub. Since, pulling the changes pulls every commit therefore, it is a better idea.
Describe the differences between forks, clones, and branches. When would you
use one instead of another?
Forks directly make a copy of a repository from someone else's GitHub profile to your profile. Clone makes a copy of someone else's repository from their GitHub profile to your computer. A branch is an extension of an existing commit in an repository which can be merged with some other branch later.
What is the benefit of having a copy of the last known state of the remote
stored locally?
To spot whether a fast forward merge would be required or we would have to solve a conflicting merge.
How would you collaborate without using Git or GitHub? What would be easier,
and what would be harder?
There are other options like Bitbucket but I have never used it. I don't know how to answer this question and I'm bored of reflections now. I want to go home and eat like a dog.
When would you want to make changes in a separate branch rather than directly in
master? What benefits does each approach have?
I find making changes in the same branch easier. Wokring with a different branch seemed like a pain in the ass. I'm still a beginner and haven't used branches so much so I don't know how to answer this question. I guess I would use a separate when I'm not sure about the changes that I want to introduce.