feat(cli): close review issues and support moved problems

This commit is contained in:
Prad Nukala committed 2026-09-30 16:23:54 -04:00
1 parent 1d77c5a8b5
commit 9c7d48aad8
3 files changed
+90 -29

No files matched your search

+23 -15
View File
@@ -2,27 +2,29 @@
* Topic issues and their problem sub-issues: the ONE reading of "is this topic
* finished", shared by close-topics.ts (closes the topic issue) and
* release-topics.ts (publishes the topic's timever release) so the two can
* never disagree about when a topic was done.
* never disagree about when a topic was done. Also the one reading of "is this
* Review issue finished", which close-topics.ts closes on.
*
* Rule: a topic is finished when it has a core set (`set:core` sub-issues) and
* every one of them is closed. Optional and deferred problems are extra credit
* and never hold a topic open. A topic with no core sub-issues is never
* finished — that would be indistinguishable from a mis-labelled problem set.
*
* Review issues (`Review <N> — <Phase>`, label `review`) are day blocks for
* the transfer phase: problems were re-parented into them from their topics
* (a GitHub issue has one parent). A topic still OWNS such a problem —
* readProblems() returns it alongside the topic's direct sub-issues, with the
* ownership recovered by apps/api/src/reviews.ts (shared with the Worker's
* catalog reconcile) — so the finished rule and the release snapshots do not
* change when a problem moves. A Review issue is finished when every one of
* its sub-issues is closed: it is a fixed assignment, so the set labels do
* not matter there.
*
* Library: side-effect-free on import; every call takes the caller's github().
*/
import type { Problem } from "../api/src/reviews.ts";
import type { GitHub } from "./github.ts";
/** One problem sub-issue, narrowed from the sub_issues payload. */
export interface Problem {
number: number;
/** `LC <num> · <Name>`. */
title: string;
/** ISO instant the issue closed; null while it is open. */
closedAt: string | null;
labels: string[];
}
export interface Core {
/** Core sub-issues, closed and open alike, lowest number first. */
all: number[];
@@ -33,11 +35,17 @@ export interface Core {
}
/**
* Every sub-issue of a topic. The sub_issues payload carries the full issue
* objects (state + labels), so no per-problem follow-up request is needed.
* Every problem a topic owns: its sub-issues plus the ones moved from it into
* a Review issue (`moved`, from movedFromTopics()). The sub_issues payload
* carries the full issue objects (state + labels), so no per-problem
* follow-up request is needed.
*/
export async function readProblems(gh: GitHub, topic: number): Promise<Problem[]> {
const problems: Problem[] = [];
export async function readProblems(
gh: GitHub,
topic: number,
moved: Map<number, Problem[]>,
): Promise<Problem[]> {
const problems = [...(moved.get(topic) ?? [])];
for await (const raw of gh.list(`/repos/${gh.repo}/issues/${topic}/sub_issues`)) {
if (!raw || typeof raw !== "object") continue;
if (!("number" in raw) || typeof raw.number !== "number") continue;