-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlesson_3_reflections.txt
19 lines (12 loc) · 1.53 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 create a remote repository rather than keeping all your work local?
Almost immediately. It's good to have a versioned copy from my files.
Why might you want to always pull changes manually rather than having Git automatically stay up-to-date with your remote repository?
Because sometimes, working on a new branch, maybe updated files will create some conflicts for my branch.
Describe the differences between forks, clones, and branches. When would you use one instead of another?
Forks are similar to clones but work only over remote repositories (GitHub). Clones can be used remoto to local or even local to local. Branches create new implementations of codes (it can be local or remote).
What is the benefit of having a copy of the last known state of the remote stored locally?
It's good to have it because of the others collaborators changes that may conflict with your current job.
How would you collaborate without using Git or GitHub? What would be easier, and what would be harder?
I would use the tools I had. It wouldn't be necessary making mergings and solve conflicts but it would be hard to handdle different people collaborating without so good tool like GitHub
When would you want to make changes in a separate branch rather than directly in master? What benefits does each approach have?
In large projects that is real necessary. The main part of the project keeps untouched until it's really necessary, besides it's possible to get the main project and transform for a specific purpose without affect the original one.