-
Notifications
You must be signed in to change notification settings - Fork 0
/
lesson_3_reflections.txt
17 lines (12 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
When would you want to use a remote repository rather than keeping all your work local?
When I want to colaborate whith other people and when I work in different computers
Why might you want to always pull changes manually rather than having Git automatically stay up-to-date with your remote repository?
I think that there isn't a cause.
Describe the differences between forks, clones, and branches. When would you use one instead of another?
The differences are that branches doesn't repeat commits like clones and forks. Between forks and clones, they are the same, but in differents platforms
What is the benefit of having a copy of the last known state of the remote stored locally?
You know where the production is, and you don't need to be connected in order to make commits.
How would you collaborate without using Git or GitHub? What would be easier, and what would be harder?
I use to colaborate using google drive. It is not a good idea because you cannot collaborate at the same time, or you can do it by creating a copy of the file and then merging it, but not automatically like git does. It is hard to learn to use git, but it is faster and easier to collaborate with it and GitHub.
When would you want to make changes in a separate branch rather than directly in master? What benefits does each approach have?
I would want to create a branch when I would like to make changes in a specific charachteristic of the code. Separating into branches have the benefit that different works are separated; doing everything in the master could be confusing, but it is easier to "merge".