Skip to content

chore(scripts): remove orphaned scripts/github-type-label.d.mts (implementation deleted in #1088, type file left behind) #7434

Description

@JSONbored

Context

Commit 01c315bcf ("chore(ci): remove the type-label GHA — the Gittensory review already applies the
type label (#1088)") deliberately consolidated issue/PR type-labeling entirely into the Gittensory
review's own resolvePrTypeLabel/ensurePullRequestLabel path, deleting the standalone
github-type-label.mjs script, its workflow, and its test as "orphaned." That commit missed
scripts/github-type-label.d.mts, a 63-line hand-written type-declaration file describing the deleted
script's exports (normalizeLabels, classifyTypeLabel, getTypeLabelDecision, readCurrentLabels,
ensureRepositoryLabel, extractClosingIssueNumbers, fetchReferencedIssues, applyTypeLabel, main).

Every other .d.mts file under scripts/ pairs with a real, present .mjs implementation (verified:
check-branding-drift.d.mts/.mjs, check-manifest-drift.d.mts/.mjs, check-mcp-release-due.d.mts/
.mjs, and every other pair in the directory all have both halves present) — github-type-label.d.mts
is the sole exception. A repo-wide grep (.github/workflows/**, scripts/**, src/**, test/**) for
"github-type-label" as of this audit turns up only the orphaned file itself; nothing imports, type-checks
against, or otherwise references it.

Requirements

  • Delete scripts/github-type-label.d.mts.
  • Before deleting, re-run a repo-wide search for github-type-label (this audit already did so and found
    nothing else, but re-verify as part of the PR in case something has landed since) — if any real
    reference is found, resolve that first and note it in the PR instead of proceeding blind.

Deliverables

  • scripts/github-type-label.d.mts removed
  • A repo-wide search for github-type-label returns no results anywhere after the change

Test Coverage Requirements

Not applicable — this is a dead-file deletion with zero runtime behavior change. The file has no .mjs
counterpart to type-check against and nothing imports from it, so there is no coverage surface to
protect or regress. If the pre-deletion re-verification step turns up an unexpected reference, that
finding (and its fix) would need its own coverage — but absent that, no new test is required here.

Expected Outcome

scripts/ contains no orphaned type-declaration files left over from #1088's cleanup; every remaining
.d.mts in the directory has a real, present implementation file.

Links & Resources

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:bugGittensor-scored bug fix — scores a 0.05x multiplier.help wantedExtra attention is needed

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions