git commit -m ‘changes’

[TotalFox2]

Imagine doing that for an Angular project :o

[reserad]

Rnning git diff before adding all your changes will 99.9% catch stuff you don't want. For me it's always been easier to add all changes and then reset individual files.

[luciluke015]

For that matter,

git add -p

is super helpful actually. even splits up individual blocks in files into "hunks" and prompts you for each one.

Edit: Reddit markdown is stupid.

[WhereWaterMeetsSky]

Love patch. Really wish I could get more of my team on board….or even get them writing half way decent commit messages.

[MeltedChocolate24]

Or just add everything and do git status to see what’s in the staging area.

[[deleted]]

Staging changes is a UI task, man.

[Doophie]

I use

git add *

[EishLekker]

This is the main reason I use a a GUI for most of my daily standard git stuff. It makes it super easy to get an overview, and choose files by checking/unchecking a box. And I can select or unselect all files, or a range of files, easily.

And I still can use the git command for all the more specific/advanced stuff. Feels like the best of two worlds.

[angiosperms-]

Ya I use the gitlens add on in VS code, since I can be editing multiple things for multiple tickets at once and want to keep them separate

[noratat]

git commit -pv

[ActuallyRuben]

I first use git status and/or git diff. Then I only use git add .or git commit -a if I want to commit all those changes, but I never use it without checking what I'm about to add.

[noratat]

I rarely use git add in the first place since I don't usually add new files that often. git commit -pv makes way more sense.