4 ms·
I like to keep Git puristic. I have only a few aliases, because I want to operate on every machine the same way. Git can be intimidating for newcomers. In the
by rwieruch 9y ago
I like to keep Git puristic. I have only a few aliases, because I want to operate on every machine the same way.
Git can be intimidating for newcomers. In the last two years, I noticed the pattern that I only use a few essential Git commands in order to resolve a handful of scenarios. I have written them up: https://www.robinwieruch.de/git-essential-commands/ https://www.robinwieruch.de/git-essential-commands/ Maybe it helps some people to get started.
- charlierudolph 9y agoI believe knowing the low level commands is very important. I don't think anyone should use Git Town without learning everything covered in your article. Git Town prints every* Git command it runs and what branch it is run on. That was my first contribution to the project as I wanted to know exactly what the tool was doing. * Git Town runs other git commands to inspect the state of things (for example: what is the current branch, are there any uncommitted changes). These are not printed but each one that changes the state (for example: checking out another branch, fetching updates, merging branches) are printed
- rwieruch 9y agoI will give it a shot! Thanks for the clarifications :)