GIT intermediate

Discover the beauty and elegance of Git! Learn to create decent, professional repositories!

Bearing the proper abstractions in mind, you know why and what should be done; It is easier then, to find the answer to how to do it.

The book gives the reader a good sense of Git's mechanics. It is particularly useful when less obvious situations occur.

The book can be read as "from zero to hero" guide, but an advanced user (being able to fully interpret the front cover) will find something valuable as well.

At first glance, Git looks like a tangle of strange commands with incomprehensible parameters. The documentation is hard to read, so the entry threshold seems high. This creates a natural temptation to scrape the bottom of the barrel: to learn just a few operations (performed from command line, graphical tool or IDE)
typical of the team's workflow.

As a result, the repository is cluttered with project versions of poor quality, many of which do not meet established standards. E.g.

• „Under construction" versions
  The changes committed „before lunch", before and after code review, etc. Ok, one can improve it a bit by using --squash option.
• Many incoherent changes in one version
  Changes that are hard to review/understand; hindering extracting/reverting parts of them.

• Repository as a commit graph.
• Refs (of any kinds) as tools for graphs growing (both local and remote).
• Immutability of the graph vs history rewriting (transplanting of the commits).
• Cooperation between local and remote repository as sharing of the subgraphs.

• commit
• index/staging area
• reset
• rebase
• fast-forward-merge
• merge conflicts