this post was submitted on 02 Sep 2024
56 points (93.8% liked)

Git

2879 readers
3 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS
Ategon@programming.dev
jnovinger@programming.dev
canpolat@programming.dev
56
Git: avoid reset --hard, use reset --keep instead (adamj.eu)
submitted 2 months ago by norambna@programming.dev to c/git@programming.dev
8 comments fedilink hide all child comments
 

via https://fosstodon.org/@adamchainz/113069875974994637

you are viewing a single comment's thread
view the rest of the comments
[–] thesmokingman@programming.dev 4 points 2 months ago

I do not actually understand the use case of —keep over the default —mixed, which I use regularly to restage patches or fuckups. I very frequently use —hard to test something out and blow it away without worrying about any changes. This whole conversation is fascinating because it highlights just how different everyone uses git and equally how bad sweeping generalizations like “—hard is something to avoid” are (without incredibly specific caveats).

It seems like —keep makes sense if you’re not using stash before trying to change history when you have local, uncommitted changes? That might be why it’s not clicking with me; any time I fuck with history I stash anything local I might want to keep.