Skip to content

Triage: duplicate and consolidatable open issues/PRs #414

Description

@mrbobbytables

Review of open issues/PRs (24 issues, 18 PRs; nearly all bot-generated by hivecommons-hive).

Issue ↔ PR pairs (each PR should close its issue; verify Fixes #N in PR bodies)

412→#413, 409→#410, 407→#408, 405→#406, 402→#403, 400→#401, 396→#397, 394→#395, 384→#385, 382→#383, 380→#381, 377→#378, 346→#347, 344→#345, 332→#333, 313→#314, 297→#298

Consolidation candidates (likely touching the same bundle-test files; merge order causes conflicts)

Duplicates / overlaps

Other

Activity

  1. mrbobbytables commented on Oct 9, 2026

    @mrbobbytables
    MemberAuthor

    Priority list

    P1: real bugs, fix first (tests depend on the fixed behavior)

    1. [quality] comment-only prow.yaml throws YAMLException instead of loading as an empty configuration (parseProwConfig trim guard misses zero-document input) #393 + [quality] parseProwConfig's empty-document arm (config.ts:373, return {}) has no end-to-end coverage through dist/index.js #394/test(bundle): drive parseProwConfig's empty-document arm (config.ts:373) through dist/index.js #395: fix the comment-only prow.yaml YAMLException, then land test(bundle): drive parseProwConfig's empty-document arm (config.ts:373) through dist/index.js #395 pinning the empty-config behavior.
    2. [quality] a 0-byte OWNERS file fails every OWNERS-reading run with "invalid OWNERS file returned from GitHub API" (decode treats content "" as missing) #404 + [quality] parseOwners's content-shape arms (owners.ts:39/41/83: whitespace-only, non-mapping and non-string-role OWNERS files) have no bundle test through dist/index.js #405/test(bundle): drive parseOwners's content-shape arms (owners.ts:39/41/83) through dist/index.js #406: fix the 0-byte OWNERS decode bug, then land test(bundle): drive parseOwners's content-shape arms (owners.ts:39/41/83) through dist/index.js #406 so its content-shape tests match the fix.

    P2: close out already-covered work (low effort)
    3. #171 + #390: confirm #390 has Fixes #171, review, and merge. Unblocks the dependabot dist-gate failures for later PRs.
    4. Issue↔PR link check: add Fixes #N to any of the 17 PRs missing it so merging auto-closes the issues.

    P3: consolidate (reduces merge conflicts)
    5. Owners/auth bundle: combine #406, #403, #401, #383, #381, #378; fold #386 in. Land after P1.
    6. Plugin and cron bundle: combine #385, #345, #347, #333, #410, #408.
    7. Small single-arm tests: batch #413, #397, #314, #298 (#395 goes with P1).

    P4: cleanup
    8. #366: replace with a dead-code removal PR for getArgumentLabels and anyLabelMatches.
    9. #40: close as stale/superseded by the bundle-test effort.
    10. #170: keep as tracking issue; update after merges.

  2. mrbobbytables commented on Oct 11, 2026

    @mrbobbytables
    MemberAuthor

    /kind cleanup

  3. added
    kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.
    and removed on Oct 11, 2026
  4. mrbobbytables commented on Oct 11, 2026

    @mrbobbytables
    MemberAuthor

    Priority list — update (2026-10-11)

    Everything in the Oct 9 list has landed: all 18 PRs merged and all 21 paired issues closed (#171, #366, #393, #404 included). Current state: 16 open issues, 16 open PRs (12 hive, 4 dependabot).

    P0: unblock CI automation

    1. Configure REPACK_APP_ID / REPACK_APP_PRIVATE_KEY repo secrets. The push-repacked-dist job added by ci: repack dist/ on dependabot branches without exposing a write token #390 fails with 'client-id' … must be set to a non-empty string, so it never repacks. chore(deps): bump js-yaml from 5.4.2 to 5.4.3 in the production-dependencies group #440 (js-yaml, a prod dep) fails the dist gate because of this. Until the secrets exist, chore(deps): bump js-yaml from 5.4.2 to 5.4.3 in the production-dependencies group #440 needs a manual npm run pack commit.

    P1: coverage-measurement fixes (land before the arm tests so their e2e hits are real)
    2. #427 (→ #426): stop the acceptance harness loading src/ into the vitest worker. Touches helpers.ts + 25 existing test files (1-line import swaps) — none of the new PRs import ownersFixtures directly, so no conflicts.
    3. #425 (→ #424): column-aware source map for test:coverage:e2e. No file overlap with #427; rebase after it and confirm the false zeros on pullRequestOwners.ts:74 / config.ts:428 / owners.ts:284 are gone.

    P2: "drive X through dist/index.js" arm tests — merge individually, no consolidation needed
    Each adds exactly one new file under __tests__/bundle/ and imports only from ./helpers; zero overlap between them, so merge order doesn't matter.
    4. #423 (→ #422), #429 (→ #428), #431 (→ #430), #433 (→ #432), #435 (→ #434), #437 (→ #436), #439 (→ #438), #445 (→ #444), #447 (→ #446), #448 (no issue — fine to merge as-is).

    P2: dependabot
    5. #441, #442, #443 — dev deps / action bumps, dist unaffected, CI green → merge.
    6. #440 — after item 1 (or manual repack).

    P3: new PR needed
    7. #386 (14 unreachable commenter-auth catch arms): the probes in auth.ts never reject, so the wrappers are dead code only reachable via vi.mock. Open a removal PR (drop the wrappers + their mock-only unit tests) rather than a coverage PR. Was slated to fold into #378, but #378 merged without it.

    P4: cleanup
    8. #40: close as stale/superseded — the bundle test suite is this.
    9. #170: keep as tracking issue; refresh after P1/P2 merge.
    10. Close this issue once P0–P2 are done.

  5. mrbobbytables commented on Oct 11, 2026

    @mrbobbytables
    MemberAuthor

    P1 done. #427 merged (1790da4, closes #426) then #425 merged (850dbb0, closes #424). Verified post-#427 that npm run test:coverage:e2e composes columns for all 52 src/ modules, the three false-zero lines now report hits (146/131/5) and the unreachable arms stay at 0, with no deflation of the statement/function/branch totals (98.56 / 94.44 / 98.59). P2 arm-test PRs (#423, #429, #431, #433, #435, #437, #439, #445, #447, #448) are unblocked.

  6. mrbobbytables commented on Oct 11, 2026

    @mrbobbytables
    MemberAuthor

    P2 done. All 10 arm-test PRs merged — #423, #429, #431, #433, #435, #437, #439, #445, #447, #448 — closing #422, #428, #430, #432, #434, #436, #438, #444, #446. Verified as a single stack on main @ 850dbb0: npm run test:coverage:e2e 72 files / 452 tests pass (98.75 / 95.34 / 98.59 / 98.73), and with #425's column-accurate map every targeted arm now registers bundle hits (incl. the || right arm at sweep.ts:179 and the ?? '' arm at labelSync.ts:133, which are branch-only). Dependabot #441, #442, #443 merged (SHA-pinned action bumps + dev deps).

    Remaining: P0 #440 (needs REPACK_APP_ID/REPACK_APP_PRIVATE_KEY or a manual npm run pack), P3 #386 (dead-code removal PR), P4 #40 (close), #170 (tracking).

  7. mrbobbytables commented on Oct 11, 2026

    @mrbobbytables
    MemberAuthor

    P3: opened #449 for #386 — removes the 14 unreachable commenter-auth catch wrappers (10 command handlers + 4 in auth.ts), deletes the 15 mock-only unit cases that pinned their messages, repacks dist/. Net −328 lines. npm run all passes (151 files / 2075 tests), unit coverage stays at 100 % lines without the mock-rejection cases, e2e src/ lines 98.73 % → 99.28 %. CI green; awaiting review.

    Remaining after #449: P0 #440 (REPACK_APP_* secrets or manual npm run pack), P4 #40 (close), #170 (tracking).

  8. mrbobbytables commented on Oct 11, 2026

    @mrbobbytables
    MemberAuthor

    P4 done. #40 closed as superseded by the bundle acceptance harness (72 files / 452 tests, 99.3 % e2e lines against dist/index.js); the real-sandbox nightly half is noted there as a separate infra-bound follow-up to #210 if ever funded. #170 given /kind cleanup (it is a self-refreshing bot digest; stays open by design).

    Final state

    before (Oct 9) now
    open issues 24 3 (#414, #386 → closes with #449, #170 living doc)
    open PRs 18 2 (#449 awaiting review, #440 blocked)

    Everything on the list is merged, closed or in a PR except:

    This issue can close once those two land.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions