---
title: "Comment by Schalk Neethling on \"Top 10 Git Commands Every Developer Should Know\" | Hashnode"
description: "Great article, Tapas. I know many people not used to working with version control systems find getting started and remembering the command hard. This is a nice"
url: "https://hashnode.com/posts/top-10-git-commands-every-developer-should-know/63f887f5679f7494ea339e3c/comment/63fb7741a13f5e02f6798171"
---

[Discussion](https://hashnode.com/posts/top-10-git-commands-every-developer-should-know/63f887f5679f7494ea339e3c)

Comment [Top 10 Git Commands Every Developer Should Know](https://hashnode.com/posts/top-10-git-commands-every-developer-should-know/63f887f5679f7494ea339e3c)

[Schalk Neethling](https://hashnode.com/@schalkneethling)

[Feb 26, 2023](https://hashnode.com/posts/top-10-git-commands-every-developer-should-know/63f887f5679f7494ea339e3c/comment/63fb7741a13f5e02f6798171)

Great article, Tapas. I know many people not used to working with version control systems find getting started and remembering the command hard. This is a nice reference for those folks.

I wanted to call your attention to one command you mentioned here that people might misunderstand from how you described it. I am referring to the git rm command.

From the docs ([git-scm.com/docs/git-rm](https://git-scm.com/docs/git-rm)), git rm will remove the file(s) from the working tree and the index. This might be what the user is after, but if they want to only undo the changes they staged, they will need to use git checkout ([git-scm.com/docs/git-checkout](https://git-scm.com/docs/git-checkout)) and reference the commit they want to checkout too. There are also neat flags like --ours and --theirs, which I only learned about recently.

[Tapas Adhikary](https://hashnode.com/@atapas)

[Feb 26, 2023](https://hashnode.com/posts/top-10-git-commands-every-developer-should-know/63f887f5679f7494ea339e3c/comment/63fb7741a13f5e02f6798171#reply-63fb7f0142967b0d40d3686c)

Great call out. I'll edit that part to make things more clear 👍