kmfkgray.blogg.se - Git visual

Although these can be useful, not all commands have them, and the purely text-based output can be quite sparse as is typical of Git's command-line interface. Some Git commands implement a -n or -dry-run flag that enables users to get some idea of how that command will affect the state of their repository. What if you could easily get a visual picture of how any Git command would impact your local repo, without interrupting your dev workflow? When -dry-runs aren't enough

This got me thinking about ways to help Git users of all experience levels understand exactly how running a specific Git command will impact their own local repo before running it. This usually leads to Googling and Stackoverflow to hopefully find someone in a parallel situation and extrapolate their solution to your local repo. It is also common practice for newbies to copy entire repos before running commands in case they end up in a state they don't know how to recover from.Įven intermediate and advanced Git users often find themselves in situations where they aren't 100% sure what the outcome of a particular command might be.

The large number of commands that Git providesĪnd despite repeatedly being told by experienced users that Git is a very "safe" tool in that it is actually quite hard to lose your work, new Git users often operate with a low-level of constant underlying anxiety that their data will be lost or corrupted around every corner.

The situational awareness required to be versatile with Git.The wide breadth of concepts that underlie Git's model (working directory, staging area, object database, Git objects, SHA-1, local repo, remote repo, DAG, branching, merging, etc, etc, etc.).In my opinion this is due to the following 3 factors: Full list of Git-Sim supported commandsĭespite its simple design under the hood, Git is a notoriously confusing tool for new devs to learn to use and understand.