Skip to content

Commit 450a1c1

Browse files
randomechoAndrew Dailey
authored and
Andrew Dailey
committed
Clarify where git reset moves HEAD, affect on stage, index
1 parent 96186d0 commit 450a1c1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

basic/index.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -691,7 +691,7 @@ <h4>
691691

692692
<h4>
693693
git reset --soft
694-
<small>moves what HEAD points to, index and staging are untouched</small>
694+
<small>moves HEAD to specified commit reference, index and staging are untouched</small>
695695
</h4>
696696

697697
<p>The first thing <code>git reset</code> does is undo the last
@@ -753,8 +753,8 @@ <h4>
753753

754754
<p>In the above example, while we had both changes ready to commit and
755755
ready to stage, a <code>git reset --hard</code> wiped them out.
756-
The working tree and stage are now reset to the point just after the
757-
commit pointed at by HEAD.</p>
756+
The working tree and staging area are reset to the tip of the current
757+
branch or HEAD.</p>
758758

759759
<p>You can replace <code>HEAD</code> with a commit SHA-1 or another
760760
parent reference to reset to that specific point.</p>

0 commit comments

Comments
 (0)