Skip to content

Repair script: skip deleted issues and shared new names - #524

Merged
jarstelfox merged 1 commit into
masterfrom
claude/repair-ambiguous
Oct 11, 2026
Merged

jarstelfox merged 1 commit into
masterfrom
claude/repair-ambiguous

Conversation

@jarstelfox

Copy link
Copy Markdown
Member

🤖

The repair script's dry run on dev, with #523's fix, crashed partway through, and it got one guess wrong before that. Nothing was written: it only lists.

  • Crash: GitHub answers 410 This issue was deleted for ifixit#34336, not 404, so the deleted-issue guard didn't catch it. It now skips both.
  • Wrong guess: it proposed FoF -> carpenter and squad-carpenter -> carpenter. Those PRs carry both old labels, so carpenter looks new on every one of them for either label, and only one can be the rename. When two old labels point at one new name in a repo, both are now listed and left alone.
Renames the dry run proposed in ifixit before the crash
"errbit" -> "sentry"
"FoF" -> "carpenter"                (now skipped)
"P-ifixit-oidc-login" -> "P-ifixit-account-login"
"skip_failures" -> "silence_failures"
"squad-carpenter" -> "carpenter"    (now skipped)

Every other stale ifixit label (about 75, mostly years-old labels that were deleted) had no single new name and is left alone.

QA

  • On dev, run bin/repair-renamed-labels with no flag. It runs to the end and lists FoF and squad-carpenter as sharing a new name.

🤖 Generated with Claude Code

The dry run on dev stopped at ifixit#34336: GitHub answers 410 for a
deleted issue, not 404, so the guard let it through and the script
crashed. It also mapped both FoF and squad-carpenter to carpenter in
ifixit: their PRs carry both old labels, so carpenter is new on every
one of them for either label. Two old labels with one new name are now
listed and left alone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jarstelfox
jarstelfox merged commit ea989a4 into master Oct 11, 2026
1 check passed
@jarstelfox
jarstelfox deleted the claude/repair-ambiguous branch October 11, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant