![]() 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.
0 Comments
Leave a Reply. |