Post AcXt1XroXQPaJmO2dc by phel@toot.cafe
 (DIR) More posts by phel@toot.cafe
 (DIR) Post #AcXov7IzyrvaNumVOK by b0rk@social.jvns.ca
       2023-12-06T19:37:42Z
       
       0 likes, 0 repeats
       
       every git command I use
       
 (DIR) Post #AcXovDJDexfZ0KvlZI by b0rk@social.jvns.ca
       2023-12-06T19:47:43Z
       
       0 likes, 0 repeats
       
       feels hard to argue that git is easy to learn when i use at a minimum 20 different git subcommands, each of which has its own weird gotchas(2/?)
       
 (DIR) Post #AcXovE5QliEZPrUGiO by penguin42@mastodon.org.uk
       2023-12-06T20:58:32Z
       
       0 likes, 0 repeats
       
       @b0rk Huh, I learnt 'git switch' from that; never used that.  But here's an example of git being hard;  'git switch -c' is the counterpoint to 'git checkout -b' - would it have been too damn hard to use the same flag???
       
 (DIR) Post #AcXovHUi6BEnz8L02C by b0rk@social.jvns.ca
       2023-12-06T20:02:40Z
       
       0 likes, 0 repeats
       
       i'm kind of curious about what people mean when they say "i just use 5 git commands", my best guess is that there are 5 main "stressful" commands (maybe commit, merge, rebase, push, and pull) and that's what folks are thinking of(3/?)
       
 (DIR) Post #AcXrW6rqltLDeKqlvM by b0rk@social.jvns.ca
       2023-12-06T21:10:28Z
       
       0 likes, 0 repeats
       
       ok I made a quick survey about which git commands you use, it's literally 1 question (run `history | grep -Eo '^(git\s+[^ ]*)' | sort | uniq -c | sort -r ` and paste the output) if enough people fill it out I will make some highly unscientific graphshttps://forms.gle/fQjQVxhQrQdu4Cd8A(4/?)
       
 (DIR) Post #AcXrW7l9SHZqPqiw7c by penguin42@mastodon.org.uk
       2023-12-06T21:27:39Z
       
       0 likes, 0 repeats
       
       @b0rk I had to take the ^ off because my history shows line numbers (but then without the ^ we get a case that's actually a parameter to tar not a git command)
       
 (DIR) Post #AcXt1XroXQPaJmO2dc by phel@toot.cafe
       2023-12-06T21:44:30Z
       
       0 likes, 0 repeats
       
       @b0rk @penguin42 I added a `cut -d' ' -f5-`in between history and the grep and that got it working for me. But I'm guessing it's probably more reliable to wrap it up in a small awk script and skip the grep too
       
 (DIR) Post #AcXttOyJpGaeMs6sqW by eliasr@social.librem.one
       2023-12-06T21:54:21Z
       
       0 likes, 0 repeats
       
       @b0rk good list! I have one more command that I found very helpful:git pull --rebase
       
 (DIR) Post #Ai2ZKpFApQX1N6RfjE by zellyn@hachyderm.io
       2023-12-06T21:48:43Z
       
       0 likes, 0 repeats
       
       @b0rk Submitted, including the horrifyingly embarrassing number of typos 😂
       
 (DIR) Post #Ai2ZKr6jtkyP9WVxrM by b0rk@social.jvns.ca
       2023-12-06T21:51:03Z
       
       0 likes, 0 repeats
       
       @zellyn i’m “git ocmmit” :)
       
 (DIR) Post #Ai2ZKsHPXZ6UmuW08G by novalis@honk.novalis.org
       2023-12-07T18:47:00Z
       
       0 likes, 0 repeats
       
       @b0rk I'm git config --global help.autocorrect 1
       
 (DIR) Post #Ai2ZKt2YiGol98Zeca by b0rk@social.jvns.ca
       2023-12-07T18:49:11Z
       
       0 likes, 0 repeats
       
       @novalis TIL
       
 (DIR) Post #Ai2ZKu5mnkzePR5kI4 by andrew@social.afontaine.dev
       2023-12-07T18:53:49.673668Z
       
       0 likes, 0 repeats
       
       @b0rk @novalis the number is the number of seconds it waits before it tries what it thinks you meant. I have it set to 5 in case I accidentally start doing something dangerous.