-
Notifications
You must be signed in to change notification settings - Fork 1
Re-cut work orphaned by the secret-purge force-push (26 PRs) #1378
Copy link
Copy link
Open
Labels
agent-taskbugSomething isn't workingSomething isn't workingci-cdci/cddependenciesPull requests that update a dependency filePull requests that update a dependency filedocumentationImprovements or additions to documentationImprovements or additions to documentationgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions codeinfrastructuremcp/agentneeds-triagepipelinepriority:highsecuritytriaged
Description
Activity
Metadata
Metadata
Assignees
Labels
agent-taskbugSomething isn't workingSomething isn't workingci-cdci/cddependenciesPull requests that update a dependency filePull requests that update a dependency filedocumentationImprovements or additions to documentationImprovements or additions to documentationgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions codeinfrastructuremcp/agentneeds-triagepipelinepriority:highsecuritytriaged
What this tracks
26 open PRs share no common ancestor with current
main: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 againstmainare 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 neededa631194 fix: give RedisCacheLayer an event-loop ownership contractis the current tip ofmainmainalready pinsactions/github-script@… # v9.0.0focus-visiblestyling present acrossapps/web/src/components/onmainSuperseded by a live, rebaseable PR
main, 2 files. Still genuinely unlanded:mainhas^1.1.16/^2.1.2, below the patched backportNeeds re-cutting from current
main— work is real and unlandedVerified absent from
main:@(security)/api/pipeline/streamAbortError)MCPOrchestrator._execute_on_server(same surface; pick one when re-cutting)apps/webdependency floors; dedupe@opentelemetry/apito 1.9.1python-joseto clear the unfixableecdsaadvisory (GHSA-wj6h-64fc-37mp)apps/weblockfile with declared rangesactions/download-artifact7 → 8 (partially applied:maincurrently carries both@v7and@v8)github/codeql-action4 → 4.37.3org_internalrunbook (docs)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.