Notes

Did you know that git...

By understanding these concepts, you can better manage your branches and commit.

Branches as Pointers:

• A Git branch is indeed a pointer, but it specifically points to the latest commit in a particular line of development. When you create a new commit on a branch, it extends that branch's history, moving its pointer forward. This does not automatically affect other branches. Each branch maintains its own independent pointer to its latest commit.

Commit History as a Directed Acyclic Graph (DAG):

• Git's commit history is structured as a Directed Acyclic Graph (DAG), where each commit is a snapshot of the repository at a specific point in time. Commits are connected through parent-child relationships, forming a graph. Branches are simply labels or pointers to specific commits within this graph. When you create a new commit on a branch, it adds a new node to the graph, and the branch pointer moves to this new commit. Other branches remain unaffected unless explicitly merged or rebased.

Independent Evolution of Branches:

• Branches evolve independently. Commits made on Branch A do not automatically appear on Branch B because each branch has its own pointer. To see changes from Branch A in Branch B, you need to merge or rebase Branch A into Branch B. This action integrates the commits from Branch A into the history of Branch B.