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         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...