Skip to main content

Git–Discard local changes

Git offers a wide range of possibilities to discard local changes. In this post I like to share some of the available options. Before I dive into the details, it is important to make the distinction between untracked and tracked files.

From the documentation:

Git has something called the "staging area" or "index". This is an intermediate area where commits can be formatted and reviewed before completing the commit.

 

Untracked files live in the git working directory but are not managed by git until you stage them.

Tracked files

Here are some options to discard changes in tracked files:

  1. Discard Changes in a Specific File: If you want to discard changes in a specific file, you can use the following command:

    git checkout -- filename

    This will replace the changes in the specified file with the last committed version of that file.

  2. Discard Changes in All Modified Files: To discard changes in all modified files in the working directory, you can use the following command:

        git checkout -- .

    The . specifies the current directory, and this command will discard changes in all modified files.

  3. Discard Uncommitted Changes and Switch Branch: If you want to switch branches and discard any uncommitted changes, you can use the following command:   

    git checkout -f branch_name

    Replace branch_name with the name of the branch you want to switch to. The -f (or --force) option is used to discard changes.

  4. Stash Changes: Another option is to use Git stash to save your changes temporarily, switch to a different branch, and then apply or drop the stash based on your needs:

    # Save changes to a stash
    git stash
    # Switch to a different branch
    git checkout branch_name
    # Apply the stash to the new branch if needed
    git stash apply
    # Or, if you don't need the stash anymore
    git stash drop

Untracked files

If you have untracked files that you want to remove, you can use the git clean command. Be cautious with this command, as it permanently deletes untracked files.

git clean -f

The -f (force) option is required to perform the clean operation.

If you want to remove both untracked files and directories, you can use the -d option:

git clean -fd

Always be careful when using git clean as it permanently deletes untracked files, and there's no easy way to recover them.

If you want to remove untracked files from the working directory but keep them in the repository (i.e., you don't want them to be tracked), you can use the following command:

git clean -fX

This will remove only the untracked files but not untracked directories. The -X option tells Git to remove only the files that are not listed in the .gitignore file.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...