3 ms·
I'm a programmer, I understand all those things well, but I struggle to use git beyond pull, commit, push. Every time I do something more than that I end up ne
by throwaway201103 6y ago
I'm a programmer, I understand all those things well, but I struggle to use git beyond pull, commit, push.
Every time I do something more than that I end up needing to google error messages, and usually end up copying my changes to a temp directory, doing a hard reset, and starting over.
- globular-toast 6y agoI assume you haven't studied git at the DAG level then. It makes a lot more sense once you do.
- blackrock 6y agoI think he chose the wrong verbs. pull should’ve been clone. commit should’ve been snap. push should’ve been commit. This way, clone (instead of pull) will make a local copy on your computer. This is your local working copy. When you are ready to save, you can “snap” shot it, and leave a little message. And you can do as much of this as you want. Then when you’re ready to merge it back to the primary database, then you can “commit” it. The whole concept of pull/commit/push seems nonsensical to me. As a layman, I can’t understand the importance of pull vs. push in this context. And this makes it difficult to explain to someone non-technical.