-
Notifications
You must be signed in to change notification settings - Fork 0
/
lesson_1_reflections.txt
23 lines (12 loc) · 1.3 KB
/
lesson_1_reflections.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
How did viewing a diff between two versions of a file help you see the bug that was introduced?
How could habing easy access to the entire history of a file make you a more efficient programmer in the long term?
What do you think are the pros and cons of manually choosing when to creat a commit, like you do in Git, vs having versions automatically saved, like Google Docs does?
Why do you think some version control systems, like Git, allow saving multiple files in one commit, while others, like Google Docs, treat each file separately?
How can you use the commands git log and git diff to view the history of files?
How might using version control make you more confident to make changes that could break something?
Now that you have your workspace set up, what do you want to try using Git for?
What are some situations when branches would be helpful in keeping your history organized? How would branches help?
How do the diagrams help you visualize the branch structure?
What is the result of merging two branches together? Why do we represent it in the diagram the way we do?
Why might you want to always pull changes manually rather than having Git automatically stay up-to-date with your remote repository?
Describe the differences between forks, clones, and branches. When would you use one instead of another?