A pull request shipped at 08:06. The daily report said nothing did.

Description and use

A PR was merged and a page shipped, but the ledger entry was missing because it was committed after the PR closed. A new rule forces ledger commits onto a fresh branch and opens a new PR, fixing the issue.

Problem

A pipeline merged a pull request and shipped a page, but the daily report failed to record the shipment because the ledger entry commit was appended after the PR was closed.

Outcome

The pipeline now reliably records shipments, and the daily report accurately reflects production changes.

Workflow

• 1. PR #793 is merged after its commit SHA passes validation.
• 2. The pipeline ships the updated page to production.
• 3. A separate commit that writes the ledger entry is appended to the PR branch after the merge.
• 4. The merge automation does not re‑merge the closed PR, so the ledger commit never reaches main.
• 5. The daily report reads the ledger, finds no entry for the day, and reports zero shipments.
• 6. The fix introduces a rule: ledger commits must be made on a fresh branch from main and opened as a new PR.
• 7. The append script now refuses to run if the target branch is already merged, requiring an explicit reason to override.

Evidence

The pipeline merged pull request #793 at 08:06 Japan time, refreshing a getting‑started page and shipping the change to production.

Source

The only thing missing was a second commit: the one that was supposed to write this row into the ledger in the first place.

Source

The merge automation only merges a pull request's commit once that exact commit SHA has passed validation — it re‑checks the SHA, not just the branch name, before merging.

Source

The commit sat on a branch nobody was going to merge again.

Source

The fix was not a retry or a bigger timeout. It was a rule about which branch a late‑arriving record is allowed to land on: cut a fresh branch from the current main, write the record there, and open a new pull request for it.

Source