We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

The Things Git Can Do (that none of the GUIs have ever told you about)

Formal Metadata

Title
The Things Git Can Do (that none of the GUIs have ever told you about)
Title of Series
Number of Parts
96
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
It took less than a decade for Git to become the de-facto standard in version control systems. Most people who use it praise its speed. Some appreciate its flexibility. Everyone criticizes its unwarranted complexity. In order to make Git more approachable, a number of GUIs have been developed on top of it. While many of them have contributed to its widespread popularity, they all share a common design flaw: sacrificing Git's true potential on the altar of user-friendliness. Regardless of how many features these tools may have, no graphical metaphor can effectively represent what was conceived for the command line. In this session I'll demonstrate exactly what Git can do for you that none of the GUI tools ever tells you about. Moving chunks of commits between branches in a single command, custom history visualizations and data recovery are only some of the things I'll demonstrate, all 100% from the command line. If you're using Git through a GUI, you're missing out. Let me show you why.