Skip to content

Re-cut work orphaned by the secret-purge force-push (26 PRs) #1378

Description

@groupthinking

What this tracks

26 open PRs share no common ancestor with current main:

$ git merge-base origin/main origin/<branch>
(empty — unrelated histories)

This is the secret-purge force-push documented in CLAUDE.md → Repo Hygiene. These branches predate it, so they are orphaned, not merely stale. No rebase recovers them — there is no shared base to rebase onto. Their diffs against main are also meaningless: computing one against an empty merge base silently degrades to a working-tree diff, which is why a two-line Dependabot bump like #1172 appears as 111 files / 15,650 lines.

All 26 are being closed because the branch cannot land. This issue exists so the work is not lost with the branch.

Already on main — no follow-up needed

PR Evidence
#1179 Landed as #1368a631194 fix: give RedisCacheLayer an event-loop ownership contract is the current tip of main
#1003 main already pins actions/github-script@… # v9.0.0
#1049, #1045 focus-visible styling present across apps/web/src/components/ on main

Superseded by a live, rebaseable PR

PR Superseded by
#1117 (brace-expansion floors) #1226 — same fix, shares ancestry with main, 2 files. Still genuinely unlanded: main has ^1.1.16 / ^2.1.2, below the patched backport

Needs re-cutting from current main — work is real and unlanded

Verified absent from main:

Low value, re-cut only if wanted: #1080, #1020, #1043 (micro-optimizations), #1242, #1241.

How to re-cut

Branch from current main, reapply the intended change by hand, and open a fresh PR. Do not attempt to rebase or cherry-pick from the orphaned branch — with unrelated histories the result is not trustworthy.

Every orphaned branch is retained and will be archive-tagged (git tag archive/<branch>) before any branch deletion, so the original work stays recoverable.

Related

The reason this backlog accumulated instead of draining is fixed separately in #1377 — the truth gate was unsatisfiable for any PR without a linked dispatch contract, so PRs could not leave draft and were re-created instead of landed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions