-
Notifications
You must be signed in to change notification settings - Fork 0
/
lesson_2_reflections.txt
41 lines (33 loc) · 2.06 KB
/
lesson_2_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
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
What happens when you initialize a repository? Why do you need to do it?
When you initialize a repository, git creates
all the setup files and structures needed to start tracking
your versions. You need to do it to show the location of the directory that you want to version control.
How is the staging area different from the working directory and the repository? What value do you think it offers?
It is an intermediate area between the wd and the repository. It is a sort of limbo for the changes you have made, so you can organize them how you'd like before you actually commit the changes.
How can you use the staging area to make sure you have one commit per logical change?
You can use the staging area to pick and choose which changes
belong together, and commit other logical changes seperately.
It gives you more control over how the changes are committed.
What are some situations when branches would be helpful in keeping your history organized? How would branches help? Branches would be helpful if
you would like to experiment with your code by adding new features, or
deeply exploring its architecture. They help because they provide an area
for you to freely change and break code without messing up the working
master.
How do the diagrams help you visualize the branch structure?
They help me visualize by being able to trace backward and
forward through. I could easily see that the head was going
to be unreachable through the diagram. I could draw diagrams
for my own projects.
What is the result of merging two branches together? Why do we represent it in
the diagram the way we do? All of the changes from the branch get incorporated
into the currently checked out branch. The way you represent it in the diagram
shows two separate tracks of work being combined into one.
What are the pros and cons of Git's automatic merging vs. always doing merges
manually?
Auto:
-Pros: Obviously convenience. You are able to quickly integrate new features
from other branches.
-Cons: Not always accurate, not as smart as expert programmers.
Manual:
-Pros: Full control
-Cons: Takes a long time.