Summary  
This chapter covers how to use the git restore command with the --staged and --worktree flags to unstage and revert file modifications that have been staged for commit, restoring both the staging area and working directory to their previous states.

General domain of usage  
Version control

Sometimes, changes are **staged** for commit, but upon further consideration, you realize that certain modifications should not be included. Luckily, it is possible to **revert staged changes** in Git, ensuring that your commits accurately reflect the intended modifications.



## Undoing Staged Changes with git restore
The `git restore` command is a powerful tool for reverting staged changes. To undo modifications in files that have been staged but **not yet committed**, you can use the following command:
```bash
git restore --staged <file>
```
Where `<file>` is the **name** of the files or its **path relative to the project directory**. The `--staged` flag here "tells" Git to restore the changes in the **staging area**. After running this command the changes in the `<file>` will be **unstaged**.





This command doesn't revert the changes in the working tree. Instead, it only unstages them.

Note

In case you want to **unstage** and then revert the changes in the **working directory**, you can use the following command:
```bash
git restore --staged --worktree <file>
```
Here is an image to make things clear:

## Example Workflow

Suppose you want to add another line with the next step of the recipe:
```
echo "7. Serve the eggs" >> recipe.txt
```

Unlike in the previous chapter, no mistake was made, so stage this change:
```
git add recipe.txt
```

However, after reconsidering **before committing**, it appears that adding this line to the recipe file is unnecessary.
Therefore, completely **revert this change**.
First, check the status of the **working tree** and **staging area**:
```
git status
```

This change is indeed staged, so run the `git restore` command with the appropriate flags to **fully** revert it:
```
git restore --staged --worktree recipe.txt
```

Finally, verify that both the **working tree** and **staging area** are **clean**:
```
git status
```

Git es el sistema de control de versiones más popular, utilizado por millones de desarrolladores en todo el mundo. Tanto si eres un desarrollador experimentado como si eres principiante, este curso te proporcionará los conocimientos y habilidades necesarios para gestionar eficientemente tus proyectos de software, colaborar con otros y dominar el arte del control de versiones.

Primero, se proporcionará una visión general de los sistemas de control de versiones en general. Posteriormente, se abordará Git y se aprenderán los conceptos básicos sobre la creación de un repositorio y la realización de cambios en él.

Ahora es momento de abordar una interacción más avanzada con Git, lo que aumentará tu eficiencia y te permitirá familiarizarte con algunos de los flujos de trabajo más comunes en Git.

Como sistema de control de versiones, Git permite revertir cambios cuando sea necesario, por lo que es momento de descubrir las técnicas en Git para deshacer cambios no preparados en el árbol de trabajo, cambios preparados e incluso revertir o sobrescribir confirmaciones.

Las ramas en Git son sumamente útiles al colaborar con otras personas, corregir errores o desarrollar ciertas funcionalidades en tu proyecto. Sin más preámbulos, exploremos todos los matices de trabajar con ramas.

Reverting Staged Changes

Undoing Staged Changes with git restore

Example Workflow