git reset --soft仅修改哈希值吗？关于其修改范围的技术问询

Great question—this is a common point of confusion with Git's reset commands, especially when it comes to what "commit history" actually refers to here. Let's break this down step by step:

What "commit history/commit refs" really means #

The third "tree" in that model is a bit loosely phrased, but it boils down to branch references (refs) and the HEAD pointer. The mention of "commit history" is from the perspective of your current branch: a branch's history is the chain of commits you get when tracing back from the branch's current pointer. When you use git reset --soft, you're moving that branch pointer, which changes what commits are considered part of the branch's "history" going forward. Crucially, the old commits aren't deleted—they just stop being referenced by this branch (they'll stick around until Git's garbage collector cleans them up if no other refs point to them).

Exactly what git reset --soft <SHA1> modifies #

To answer your specific question: yes, the changes are almost entirely limited to updating pointer files, but there's a small nuance with HEAD:

• .git/refs/heads/<your-branch>: If you're on the master branch, this file's content (the SHA-1 hash of the commit the branch points to) gets replaced with the <SHA1> you specified. This is the core action—moving the branch's pointer.
• .git/HEAD: If you're in a detached HEAD state (where HEAD directly points to a commit hash instead of a branch), HEAD's content will be updated to your target SHA-1. If you're on a normal branch (HEAD points to the branch ref, e.g., ref: refs/heads/master), then HEAD itself doesn't change—only the branch ref file does, and HEAD indirectly points to the new commit via the branch.

That's it! git reset --soft doesn't touch your working tree files or the staging area (index) at all—all changes you had staged before the reset stay staged, ready to be committed again if you want.

Why "history" is the right word here #

Even though you're just moving a pointer, from the branch's perspective, its "history" has changed. For example:

Suppose your master branch was pointing to commit C, with a history of A → B → C. After git reset --soft A, master now points to A, so the branch's visible history is just A. Commits B and C still exist in Git's database, but they're no longer part of master's history unless you reference them directly.

So when the model says --soft modifies "commit history", it's referring to the perceived history of the current branch, not rewriting or deleting commit objects themselves.

内容的提问来源于stack exchange，提问作者jsstuball