3 ms·

How is git intimidating? It's one of the most user friendly pieces of CLI applications out there, offers a myriad of ways to "ctrl z" and has proper documentati

How is git intimidating? It's one of the most user friendly pieces of CLI applications out there, offers a myriad of ways to "ctrl z" and has proper documentation. Problem is people don't get trained or don't want to learn. They learn "git pull" and "git commit" and then think they know how it works.

EForEndeavour 7y ago
I honestly can't tell if you're serious. Some things off the top of my head that are in my opinion not at all trivial for even intermediate git users: - How do you fix a typo in the commit message of the second-last commit that you pushed to remote? - I accidentally committed something to the wrong branch. What's the best way to uncommit it from that branch and commit it to the right branch? - What are the differences between the working tree, directory tree, index, and staging area? - How do I "un-add" a file I just staged? - I've heard "git reflog" is useful. What is it?
- pearjuice 7y ago
  If you have had any interaction beyond the basics of git those are trivial to solve. - git rebase -i HEAD~2 -- interactive rebase of last 2 commits then read the help you get (use reword on the commit you want to change, needs force push because rewriting history) - various ways to do this but easiest is: checkout correct branch, cherry-pick commit you want and then hard reset your faulty branch HEAD~1 (you can also soft reset, keep it staging and then checkout correct branch and commit) - these are all terms you should know if you are using git in my opinion because the commands et cetera will assume you know what they mean. I think it comes with every beginners git tutorial? - I am pretty sure git status will tell you how to do this by default (which shows staging area) - this is also properly documented and something a good git guide will gloss over Maybe I am biased because I use git on a daily basis but I don't think any of these are hard. Anyone who calls themselves an intermediate git user should be able to answer these questions from the top of their head. If you don't, no problem, you can easily Google them and you will notice that they are very straightforward and simple. I am not even sarcastic, git is very simple software (in terms of usage and help/documentation available).

EForEndeavour 7y ago

I honestly can't tell if you're serious. Some things off the top of my head that are in my opinion not at all trivial for even intermediate git users: - How do you fix a typo in the commit message of the second-last commit that you pushed to remote? - I accidentally committed something to the wrong branch. What's the best way to uncommit it from that branch and commit it to the right branch? - What are the differences between the working tree, directory tree, index, and staging area? - How do I "un-add" a file I just staged? - I've heard "git reflog" is useful. What is it?

pearjuice 7y ago
If you have had any interaction beyond the basics of git those are trivial to solve. - git rebase -i HEAD~2 -- interactive rebase of last 2 commits then read the help you get (use reword on the commit you want to change, needs force push because rewriting history) - various ways to do this but easiest is: checkout correct branch, cherry-pick commit you want and then hard reset your faulty branch HEAD~1 (you can also soft reset, keep it staging and then checkout correct branch and commit) - these are all terms you should know if you are using git in my opinion because the commands et cetera will assume you know what they mean. I think it comes with every beginners git tutorial? - I am pretty sure git status will tell you how to do this by default (which shows staging area) - this is also properly documented and something a good git guide will gloss over Maybe I am biased because I use git on a daily basis but I don't think any of these are hard. Anyone who calls themselves an intermediate git user should be able to answer these questions from the top of their head. If you don't, no problem, you can easily Google them and you will notice that they are very straightforward and simple. I am not even sarcastic, git is very simple software (in terms of usage and help/documentation available).