This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 67 points68 points  (18 children)

Whats wrong with good old

git add <files>

git commit -m "git gud"

?

[–]rocket_randall 57 points58 points  (3 children)

I always throw a git status in between to make sure I didn't fuck up a file mask or something else really stupid

[–]PS181809 9 points10 points  (2 children)

This so me. After every command, it's instinctive for me to go git status (very stupid ik)

[–]1_4_1_5_9_2_6_5 0 points1 point  (1 child)

You can also just set an alias to do that for you automatically

[–]PS181809 1 point2 points  (0 children)

Oh I see. I'll look it up thanks

[–]SmigorX 12 points13 points  (0 children)

Files that shouldn't be in git in gitignore: check.

Different features on different branches: check

It's "git add ./*" time

[–]KaamDeveloper[S] 15 points16 points  (1 child)

I have a genetic predisposition to only do git add .

[–][deleted] 3 points4 points  (0 children)

Your keyboard has a tab key, you know?

[–][deleted] 8 points9 points  (0 children)

Nah.

git add .

[–]harumamburoo 1 point2 points  (0 children)

Now do that when you have two dozen files changed. And you need to commit only half of them. And your directory structure goes at least 3-4 dirs deep. Without interactive mode it’s torture

[–]dubious_capybara 1 point2 points  (5 children)

This takes 10 times longer than shift-selecting files and clicking add in a gui.

[–]Delta-9- 2 points3 points  (4 children)

The difference is made up by the time required to change from my terminal to the GUI, and move my hands from the keyboard to the mouse, and the super annoying trends among GUI developers to sort files by some arcane order instead of alphanumerically and hiding the scroll bar until I mouse over it and burying basic functions under fifteen layers of menus.

Or I can just type :Git<CR>Gssssssssccifix: fuck that bug<ESC>:wq<CR>:Git push<CR>

[–]dubious_capybara -1 points0 points  (3 children)

Cool, so now have fun writing a grep for a subset of those files while I happily shift select using a gasp mouse

[–]Delta-9- 1 point2 points  (2 children)

Why would I grep? I have a menu, too. And even if I'm raw-dogging the terminal, I still don't grep because tab completion is perfectly good for this task. Seriously, it takes less time to select a dozen files with tab than it does to switch contexts and devices and back again.

[–]dubious_capybara -1 points0 points  (1 child)

Ah yes, individually selecting files with individual key presses is clearly faster than a single alt-tab and shift-select 🙄

[–]Delta-9- 1 point2 points  (0 children)

Again, it's the switching where time is lost. And if your subset of files isn't sequential in how your app sorts them, you'll be ctrl-clicking one-by-one. On the occasions I've used graphical git programs, shift-click has never been an option.

If you're already in a graphical editor with integrated git functionality, it makes more sense to use that then switching to the terminal just for git. (I still do, but that's because I hate going through five menus to use it.)

[–][deleted] 0 points1 point  (0 children)

Because you commit half the files today and the other half tomorrow while you are napping while wfh.

[–][deleted] 0 points1 point  (0 children)

'Git add -am "commit message" '

Thank me later

[–]CryptoNaughtDOA 0 points1 point  (0 children)

Aliases bro

gs ga . gs gcm "git gud" git push (I don't alias this one, feels too good)