DEV Community

Gökçer Altuntaş
Gökçer Altuntaş

Posted on

We Thought It Was a Cache Bug. It Was Actually a Stale Clone.

When a recent code change does not appear where you expect it to, cache is often the first thing that comes to mind.

And sometimes cache really is the problem.

But before clearing everything, rebuilding the application, restarting containers, or digging into deployment settings, there is a much simpler check worth doing first:

Make sure you are actually running the code you think you are running.

Start with the repository

A few basic Git commands can quickly tell you what state your local repository is in:


bash
git status
git branch --show-current
git log -1 --oneline
Enter fullscreen mode Exit fullscreen mode

Top comments (0)