lesson_2_reflection.txt

What happens when you initialize a repository? Why do you need to do it?

- It creates an empty git repository (the .git folder which contains repository metadata)
- It makes no commit for you.

How is the staging area different from the working directory and the repository?
What value do you think it offers?

- Working directory is the file contents of the folder housing the repository
- Staging area is the area where you collect the files you want to be in your next commit
- Repository is the historical commits of the files inside your working directory, plus your working directory.

How can you use the staging area to make sure you have one commit per logical
change?

- You select to add only the files that are involved with one logical commit, and then you commit.

What are some situations when branches would be helpful in keeping your history
organized? How would branches help?

- New versions.
- Long bug fixes.
- Exprerimental feagures.
- Slightly different behavior of current program.


How do the diagrams help you visualize the branch structure?

- We can see all the branches
- We can see who is working on what
- Keep track of which commits are in which diagram

What is the result of merging two branches together? Why do we represent it in
the diagram the way we do?

- Changes from both brances are present a commit and one branch.
- We represent it this way to show from which branches we merged.

What are the pros and cons of Git’s automatic merging vs. always doing merges
manually?

- Saves time.
- Prevents erroneous merges.