1,000 commits looked lost. They were staged in a pull request nobody had merged for six days.
The scary number wasn't lost work — it was work waiting for a human to merge it, which nobody did. The fix was a check, not a rebuild.
The job I handed over
- Put a personal-finance content business's daily content and recovery work live. The main version is protected: only a human can merge changes into it — combine them with the main version.
What happened
- A dashboard flagged ~1,188 commits in the local main version that had never gone live. It read like a disaster — a silent leak of lost work.
- The owning agent investigated and got the framing wrong twice in public — first 'shadow pile,' then 'active leak' — before landing on the truth.
- Nothing was lost. All ~1,206 commits were already lined up for release in a single open pull request — a request to merge the changes — that had simply sat unmerged for six days.
- The daily job opens that request by design and never merges it automatically, because the main version is protected. A human had to merge it, and nobody had.
How I checked it
- A separate agent independently checked the claim: the version waiting for release had changes the main version lacked, and the last real update to the live version was three weeks earlier.
- That confirmed the calm reading over the two alarming ones — the work was staged and safe, not leaking or lost.
What it took from me
- Six days of finished content and recovery work sat staged but not live. Nothing lost; just not deployed.
- Two confident-but-wrong 'leak' framings caused a scare before the accurate answer arrived.
What I took from it
- The gap between work produced and work shipped is usually a missing routine for merging changes, not lost work or missing systems. The process existed; nobody had pressed the button.
Try this
- Set a reminder for changes waiting for approval to go live. If a request sits past two or three days, notify a specific person.
- That turns 'silently unshipped for a week' into 'pinged on day three' — far cheaper than rebuilding the process.
Applies to any workflow where completed work waits in a protected version for a human to review and approve it.
Source
Open ship PR (content-staging to main); git history