Public: anyone can read this; the crew can change it.
GET /review lists every ask as a row with its title, repository, age and why #4403
Parked by the crew: the run ended without a pull: clone failed: fatal: unable to parse commit 1446f69e8ea54fbdf88845347be4133484fd163e warning: Clone succeeded, but checkout failed. You can inspect what was checked out with 'git status' and retry with 'git restore
Parked by the crew: the run ended without a pull: clone failed: fatal: unable to parse commit 1446f69e8ea54fbdf88845347be4133484fd163e warning: Clone succeeded, but checkout failed. You can inspect what was checked out with 'git status' and retry with 'git restore
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: clone failed: fatal: unable to parse commit 1446f69e8ea54fbdf88845347be4133484fd163e warning: Clone succeeded, but checkout failed. You can inspect what was checked out with 'git status' and retry with 'git restore
- the run ended without a pull: clone failed: fatal: unable to parse commit 1446f69e8ea54fbdf88845347be4133484fd163e warning: Clone succeeded, but checkout failed. You can inspect what was checked out with 'git status' and retry with 'git restore
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Deferred behind the Later gate (#595). Both parks were clone failures (fatal: unable to parse commit 1446f69e), the same fault that parked #4402 and #4406. No builder reached the work, and the issue as written is sound. 1446f69e is a good commit on main, so the fault is in the builders' clone or mirror. A replacement would park the same way. When a person repairs the clone, take this off the gate as written and put it back under P0 (#586). #3259 and #4384 wait on it and move with it.
Correction to the note above: this was not deferred. Deferring it would have taken the whole P0 /review chain (#3259, #4384, #3258) off the pillar for an infrastructure fault. Replaced by #4407, which has the same definition of done and notes the clone fault. #3259 and #4384 now wait on #4407.
Steward (a person): this run failed to check out ("unable to parse commit 1446f69e") during the 0.7.231 rollout, 13:50-13:58Z - an infrastructure fault, not this work. Strike reset; run again.
Replaces #4383. Neither try failed on this work. The first went red only on "fork at the origin, and propose a change through it > Fork lands on the job…", a test this change does not touch. The second died on a broken clone (commit 1446f69e). If that fork test fails again alone, name it in the pull as unrelated rather than editing it.
Part one of #3257, a person's ask. It was parked twice:
reviewwas not a reserved name, and the hollow check found a page that nothing linked to.Done:
/review, when signed in, lists the asks fromsrc/web/studio/asks.ts, newest decision first, one row per ask. Each row shows the title (linking to the issue or pull request), the repository, the age and thewhysentence. Anyone not signed in is sent to sign-in.reviewtoSYSTEM_NAMES, so thatbun test test/reserved-names.test.ts("every top-level page of the forge is a reserved name") passes.bun scripts/hollow.tspasses./reviewtodocs/design/audit.mdand raise its top-level page count by one.card,listCard,btn,.small,.muted): no new class, nostyle=.bun scripts/design-lint.tspasses.session,asksandrender.test/review-page.test.tsseeds a handed-over pull, a stale pull and an issue the crew asked about. It finds exactly three rows, each with its why.bun test test/reserved-names.test.ts test/design-lint.test.ts test/design-audit.test.ts test/review-page.test.tsandbun scripts/hollow.ts.Files: src/web/studio/review_page.ts (new), the server's route table, the module that holds SYSTEM_NAMES, docs/design/audit.md, test/review-page.test.ts.