Home/ Questions/Q 37460
Next
In Process
hari
  • 0
Asked: 2022-03-29T02:03:38+00:00 In:

How do I undo ‘git add’ before commit?

  • 0

How do I undo ‘git add’ before commit?

commitgit
Share

    Related Questions

    Leave an answer

    You must login to add an answer.

    Need An Account,

    2 Answers

    1. Undo Git Add using restore

      The easiest way to undo your git add command is to use the “git restore” command with the “–staged” option and specify the file you want to unadd.

      $ git restore --staged <file>

      As an example, let’s say that you are on a branch named “feature” and that you have recently added a new file to your staging area.

      In order to bring back the file to the working directory, we can execute the “git restore” command with the “–staged” option.

      $ git restore --staged another-file

      you have successfully undone your “git add” command using the restore one!

      Now you can modify your file, add it again and commit it if you want.

      • 0
    2. This answer was edited.

      You can undo git add before commit with

      git reset <file>

      which will remove it from the current index (the “about to be committed” list) without changing anything else. You can use

      git reset

      without any file name to unstage all due changes. This can come in handy when there are too many files to be listed one by one in a reasonable amount of time. In old versions of Git, the above commands are equivalent to git reset HEAD <file> and git reset HEAD respectively, and will fail if HEAD is undefined (because you haven’t yet made any commits in your repository) or ambiguous (because you created a branch called HEAD, which is a stupid thing that you shouldn’t do). This was changed in Git 1.8.2, though, so in modern versions of Git you can use the commands above even prior to making your first commit:

      “git reset” (without options or parameters) used to error out when you do not have any commits in your history, but it now gives you an empty index (to match non-existent commit you are not even on)

      • 0