Hosting Operations

Show Files Changed Since Last Good Release

A new release is suspect, and you need a quick list of files changed after the last stable release.

Command

cd /lab/git-recovery-rollback && git diff --name-status release-2026-06-25-1000..HEAD

What changed

Nothing changes. Git lists files changed between the previous release tag and HEAD.

Danger

safe

When to use it

Use when deciding whether a rollback is likely to touch code, config, migrations, or release metadata.

When not to use it

Do not use this as proof of root cause; it only narrows the changed surface.

Undo or recovery

No undo needed because this command is read-only.

Expected output

A name-status list including app/config.yml, db/migrate.sql, public/index.html, and release metadata.

demo script

Disposable terminal steps

cd /lab/git-recovery-rollback && git diff --stat release-2026-06-25-1000..HEAD
cd /lab/git-recovery-rollback && git diff --name-status release-2026-06-25-1000..HEAD

Terminal transcript Demo JSON

simulated output

What it looks like

disposable vessel

::fixture-ready::
$ cd /lab/git-recovery-rollback && git diff --stat release-2026-06-25-1000..HEAD
 app/config.yml                   | 4 ++--
 db/migrate.sql                   | 1 +
 public/index.html                | 2 +-
 releases/2026-06-25-1030/VERSION | 2 ++
 4 files changed, 6 insertions(+), 3 deletions(-)
::exit-code::0
$ cd /lab/git-recovery-rollback && git diff --name-status release-2026-06-25-1000..HEAD
M	app/config.yml
A	db/migrate.sql
M	public/index.html
A	releases/2026-06-25-1030/VERSION
::exit-code::0

YouTube Short

What changed since good?

Diff the suspect release against the last known-good tag. Now the rollback discussion has a file list.

experiments

A/B tests to run

Metric: save_rate

A: Compare suspect against good.

B: Rollback scope starts with changed files.