3 ms·
Excellent ideas! I agree with you on all fronts, exception git add --all && git commit. I don't believe those should be joined at the hip, because staging and
by etripe 6y ago
Excellent ideas!
I agree with you on all fronts, exception git add --all && git commit. I don't believe those should be joined at the hip, because staging and committing should be two distinct actions/decisions. Defaulting to including everything would lead to too many human errors and would therefore be dangerous in my opinion.
A distinct flag like git commit --all -m "foo" might be OK in my book. Possibly even adding some git config --global commit.all [default|confirm] or something.
Then again, who am I?
- grey-area 6y agoYes I don’t think they can change the default now but many many people operate this way (commit everything not ignored), so most of the time don’t need to separate stage and commit (I agree there needs to be a way to do it, but I use it rarely). My preference would be a command like git save, but a flag would be fine I guess. This is a concept that most beginners don’t really want or need. Ideally git should evolve so that beginners can learn say 5 standard commands without args, and that’s enough to get on with their work. Working should be as simple as: git save, git amend, git tag, git push Make everyday use simple and easy.
- etripe 6y agoI'd personally also love a config flag (enabled by default, perhaps) that offers more explanation about what the commands actually do as you run them. In other words, "explain like I'm five" logging or "tutorial mode".