-
Notifications
You must be signed in to change notification settings - Fork 0
/
lesson-2-reflection-prompts.txt
27 lines (19 loc) · 1.38 KB
/
lesson-2-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
What happens when you initialize a repository? Why do you need to do it?
How is the staging area different from the working directory and the repository?
What value do you think it offers?
Staging area just are area that temporary save your file. When we make sure that this file is finished the logical change, we will upload this to repository.
Working directory is just a observer thant observe the organization about the file.
How can you use the staging area to make sure you have one commit per logical
change?
If we still not finish the logical change yet, we should put the code on the staging area.
What are some situations when branches would be helpful in keeping your history
organized? How would branches help?
If this idea is not a offical version and just for the experiment, branches function is a good choose to use.
How do the diagrams help you visualize the branch structure?
Because some commit and branch are unreachable, we use diagrams to fully understand the whole diagram of the branch structure.
What is the result of merging two branches together? Why do we represent it in
the diagram the way we do?
If our experiment are good, of course we want to merge branches together.
What are the pros and cons of Git's automatic merging vs. always doing merges
manually?
Sometimes, some context are modify by two people at the same time. Do merge manually can efficiently this problems.