-
Notifications
You must be signed in to change notification settings - Fork 0
/
lesson_2_reflections.txt
29 lines (16 loc) · 1.64 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
What happens when you initialise a repository? Why do you need to do it?
When we initialise a repository git creates a .git file. However no commits are added.
Initialising a repository is the first step before adding anything to it.
How is the staging area different from the working directory and the repository? What value do you think it offers?
Staging Area is a temporary platform which kind of links the working directory and the repository. It helps in selecting a few files(offers selectivity) in adding to a repo.
How can you use the staging area to make sure you have one commit per logical change?
We can use the git diff to check the new thing added.
What are some situations when branches would be helpful in keeping your history organized? How would branches help?
When we need to make subtle changes which have a risk of failing, then it may be better to do that off the master branch.
Branches help by keeping the master branch unchanged and by providing a neat label for the new testing feature.
How do the diagrams help you visualise the branch structure?
Diagrams help simplify the the branch structure and we can easily know which commit is in what branch.
What is the result of merging two branches together? Why do we represent it in the diagram the way we do?
Merging two branches in a way incorporates both developments into one commit. It is represented by two paths merging to form one stem again
What are the pros and cons of Git's automatic merging vs. always doing merges manually?
Git's automatic meging saves time. Manual merging however maybe required often as Git does not do the painful job of actually verifying two branches.