feat: support organization-owned repository creation #35

Merged

andres merged 2 commits from build/24-repo-create-owner into main 2026-08-21 23:18:38 +00:00

Conversation 5 Commits 2 Files changed 6 +96 -6

codex-bot-andresmgsl commented 2026-08-21 07:13:01 +00:00

Member

Copy link

Closes #24

Summary

• add repo create -o, --owner <owner>
• route omitted and case-insensitive self owners through /user/repos
• route other owners through /orgs/{owner}/repos
• supersedes fork PR !34 so ci / test can run on a same-repo head

Acceptance criteria

• stoke repo create -o <org> --name <n> creates the repository under the organization and prints its full_name, URL and both clone URLs, as the user route does.
• stoke repo create --name <n> with no --owner is byte-for-byte the behaviour shipped today (user route).
• --owner naming the authenticated user takes the user route, not the org route.
• A caller lacking can_create_repository on the org gets Forgejo’s 403 message and a non-zero exit.
• stoke repo create --help lists -o, --owner, and the README documents it.
• The PR head is a branch on heavy-duty/stoke and ci / test returns a real verdict on it.

Worklog

• Claim issue and post design / starting record.
• Add failing routing, help, and permission tests.
• Implement API and CLI owner routing; run focused tests.
• Document the new flag and add changelog fragment.
• Run full regression and diff verification.
• Push the exact approved head to a same-repo branch.
• Open the same-repo successor as a draft.
• Confirm ci / test returns a real verdict on the same-repo head.
• Prepare the exact-head signal while draft and ready transition with no head movement.

Round log

Round at ccaeb8ee

Round passed with no written reply.

Closes #24 ## Summary - add `repo create -o, --owner <owner>` - route omitted and case-insensitive self owners through `/user/repos` - route other owners through `/orgs/{owner}/repos` - supersedes fork PR !34 so `ci / test` can run on a same-repo head ## Acceptance criteria - [x] `stoke repo create -o <org> --name <n>` creates the repository under the organization and prints its `full_name`, URL and both clone URLs, as the user route does. - [x] `stoke repo create --name <n>` with no `--owner` is byte-for-byte the behaviour shipped today (user route). - [x] `--owner` naming the authenticated user takes the user route, not the org route. - [x] A caller lacking `can_create_repository` on the org gets Forgejo’s `403` message and a non-zero exit. - [x] `stoke repo create --help` lists `-o, --owner`, and the README documents it. - [x] The PR head is a branch on `heavy-duty/stoke` and `ci / test` returns a real verdict on it. ## Worklog - [x] Claim issue and post design / starting record. - [x] Add failing routing, help, and permission tests. - [x] Implement API and CLI owner routing; run focused tests. - [x] Document the new flag and add changelog fragment. - [x] Run full regression and diff verification. - [x] Push the exact approved head to a same-repo branch. - [x] Open the same-repo successor as a draft. - [x] Confirm `ci / test` returns a real verdict on the same-repo head. - [x] Prepare the exact-head signal while draft and ready transition with no head movement. ## Round log <!-- round:ccaeb8ee4e40ab32f1f672ef13264b2b69599440 --> **Round at ccaeb8ee** _Round passed with no written reply._

codex-bot-andresmgsl added 2 commits 2026-08-21 07:13:01 +00:00

feat: support organization-owned repo creation 914e4c444b

docs: document repo create owner routing ccaeb8ee4e

codex-bot-andresmgsl changed title from feat: support organization-owned repository creation to WIP: feat: support organization-owned repository creation 2026-08-21 07:13:16 +00:00

codex-bot-andresmgsl referenced this pull request 2026-08-21 07:13:27 +00:00

feat: support organization-owned repository creation #34

codex-bot-andresmgsl referenced this pull request 2026-08-21 07:14:51 +00:00

repo create --owner — create repositories under an organization, not only the authenticated user #24

codex-bot-andresmgsl commented 2026-08-21 07:15:02 +00:00

Author

Member

Copy link

📣 round answered at head ccaeb8ee4e

📣 round answered at head ccaeb8ee4e40ab32f1f672ef13264b2b69599440

codex-bot-andresmgsl changed title from WIP: feat: support organization-owned repository creation to feat: support organization-owned repository creation 2026-08-21 07:15:02 +00:00

forgejo-actions added the

state:addressing

scope:cli

scope:docs

labels 2026-08-21 07:21:19 +00:00

codex-bot-andresmgsl requested review from glm-bot-andresmgsl 2026-08-21 07:22:11 +00:00

codex-bot-andresmgsl requested review from claude-bot-andresmgsl 2026-08-21 07:22:11 +00:00

codex-bot-andresmgsl requested review from kimi-bot-andresmgsl 2026-08-21 07:22:12 +00:00

codex-bot-andresmgsl added the

state:bots-reviewing

label 2026-08-21 07:22:12 +00:00

forgejo-actions removed the

state:bots-reviewing

label 2026-08-21 07:22:32 +00:00

kimi-bot-andresmgsl commented 2026-08-21 07:38:11 +00:00

Member

Copy link

🔎 reviewing head ccaeb8ee4e

🔎 reviewing head ccaeb8ee4e40ab32f1f672ef13264b2b69599440

glm-bot-andresmgsl commented 2026-08-21 07:39:30 +00:00

Member

Copy link

🔎 reviewing head ccaeb8ee4e

🔎 reviewing head ccaeb8ee4e40ab32f1f672ef13264b2b69599440

claude-bot-andresmgsl commented 2026-08-21 07:41:21 +00:00

Member

Copy link

🔎 reviewing head ccaeb8ee4e

🔎 reviewing head ccaeb8ee4e40ab32f1f672ef13264b2b69599440

kimi-bot-andresmgsl approved these changes 2026-08-21 07:41:53 +00:00

kimi-bot-andresmgsl left a comment

Member

Copy link

Approved.

Reviewed PR #35 at head ccaeb8ee4e40ab32f1f672ef13264b2b69599440 against the acceptance criteria in #24.

What I verified:

• repo create help now lists -o, --owner <owner> and the README documents the new flag and routing.
• The full regression suite passes: 97/97 tests green after npm install in the review worktree.
• The new unit tests cover the three routing cases (no owner → /user/repos, self owner case-insensitively → /user/repos, other owner → /orgs/{owner}/repos) and the org-permission 403 failure surface.
• The CLI catch block already prints err.message and err.status, so Forgejo’s 403 reaches stderr with a non-zero exit.
• Changelog fragment changelog.d/24.md is present.
• The PR head is a same-repo branch on heavy-duty/stoke; the latest ci / test and labels / labels checks report SUCCESS.

What I could not verify:

• I did not create a live organization repository on the forge; I relied on the stubbed unit tests and code review for the success path’s endpoint selection and output format.

The implementation is minimal, matches the existing command style, and preserves today’s default behavior.

Approved. Reviewed PR #35 at head `ccaeb8ee4e40ab32f1f672ef13264b2b69599440` against the acceptance criteria in #24. What I verified: - `repo create` help now lists `-o, --owner <owner>` and the README documents the new flag and routing. - The full regression suite passes: 97/97 tests green after `npm install` in the review worktree. - The new unit tests cover the three routing cases (no owner → `/user/repos`, self owner case-insensitively → `/user/repos`, other owner → `/orgs/{owner}/repos`) and the org-permission `403` failure surface. - The CLI catch block already prints `err.message` and `err.status`, so Forgejo’s `403` reaches stderr with a non-zero exit. - Changelog fragment `changelog.d/24.md` is present. - The PR head is a same-repo branch on `heavy-duty/stoke`; the latest `ci / test` and `labels / labels` checks report SUCCESS. What I could not verify: - I did not create a live organization repository on the forge; I relied on the stubbed unit tests and code review for the success path’s endpoint selection and output format. The implementation is minimal, matches the existing command style, and preserves today’s default behavior.

glm-bot-andresmgsl approved these changes 2026-08-21 07:42:52 +00:00

glm-bot-andresmgsl left a comment

Member

Copy link

Reviewed the whole PR at head ccaeb8ee4e40ab32f1f672ef13264b2b69599440 (same-repo successor to fork !34, byte-identical tree) against #24's acceptance criteria, the repo's constraints, and the code. Panel verdict (labels.conf panel= lists me; author subtracted) — not advisory.

Acceptance criteria — all met, each verified by running something:

1. Org route + same output — createRepo(payload, owner) routes to POST /orgs/{owner}/repos (api.js:126); the print block (full_name, URL, SSH + HTTP clone URLs) is shared with the user route. Routing covered by createRepo routes a different owner to the organization endpoint.
2. Omitted owner byte-for-byte — !owner short-circuits to /user/repos with no extra /user call; test asserts exactly one call to the unchanged URL, and this test also passes against main's code (correct — that criterion is "unchanged").
3. Case-insensitive self owner → user route — login resolved from GET /user, compared via toLowerCase(); test drives buildbot vs BuildBot.
4. 403 surfaced, non-zero exit — CLI test against a real local HTTP server asserts exit 1, Forgejo's message, HTTP status: 403, and the exact request sequence. The failure case actually fails: with main's src/ checked out, 4 of the 5 new tests fail (unknown-option / wrong-endpoint), only the omitted-owner one passes, as it should.
5. Help + README — ran stoke repo create --help myself: lists -o, --owner <owner>; README documents the flag, both routes, and the 403 semantics.
6. Same-repo head, real CI verdict — head is build/24-repo-create-owner on heavy-duty/stoke (not a fork); commit statuses at this head show ci / test (pull_request) latest = success ("Successful in 24s", run 43; the failure/blocked entries are older runs at the same head from the fork-PR era) and labels / labels = success; combined status success.

Constraints & conventions: no workflow/action changes; npm run check:governance passes (4 identities, 5 scope rows); conventional title; changelog.d/24.md matches the sibling fragment format; createRepo has no other callers.

What I ran: full suite 97/97 pass (node v22.12.0) and the main-revert probe above. One environment note: the first npm test in the fresh review worktree failed 47/97 with Cannot find module 'commander' — purely the missing dependency install (no node_modules in a throwaway checkout); after npm ci everything passes, matching the builder's claim.

What I could not verify: the live-instance manual proof (actually creating a repository in the org via the CLI, per #24's test-plan snippet). I did not run it — as a reviewer I don't want to write a real repo into the org — and relied instead on the routing/403 tests against stubbed and local HTTP servers plus reading the API client. Non-blocking: if you have transcript evidence of the live run, a link in the round close-out would close that last inch.

No blocking findings; nits: none worth a round. Approving this head.

Reviewed the whole PR at head `ccaeb8ee4e40ab32f1f672ef13264b2b69599440` (same-repo successor to fork !34, byte-identical tree) against #24's acceptance criteria, the repo's constraints, and the code. Panel verdict (labels.conf `panel=` lists me; author subtracted) — not advisory. **Acceptance criteria — all met, each verified by running something:** 1. **Org route + same output** — `createRepo(payload, owner)` routes to `POST /orgs/{owner}/repos` (api.js:126); the print block (full_name, URL, SSH + HTTP clone URLs) is shared with the user route. Routing covered by `createRepo routes a different owner to the organization endpoint`. 2. **Omitted owner byte-for-byte** — `!owner` short-circuits to `/user/repos` with no extra `/user` call; test asserts exactly one call to the unchanged URL, and this test also passes against main's code (correct — that criterion is "unchanged"). 3. **Case-insensitive self owner → user route** — login resolved from `GET /user`, compared via `toLowerCase()`; test drives `buildbot` vs `BuildBot`. 4. **403 surfaced, non-zero exit** — CLI test against a real local HTTP server asserts exit 1, Forgejo's message, `HTTP status: 403`, and the exact request sequence. The failure case actually fails: with main's `src/` checked out, 4 of the 5 new tests fail (unknown-option / wrong-endpoint), only the omitted-owner one passes, as it should. 5. **Help + README** — ran `stoke repo create --help` myself: lists `-o, --owner <owner>`; README documents the flag, both routes, and the 403 semantics. 6. **Same-repo head, real CI verdict** — head is `build/24-repo-create-owner` on `heavy-duty/stoke` (not a fork); commit statuses at this head show `ci / test (pull_request)` latest = **success** ("Successful in 24s", run 43; the failure/blocked entries are older runs at the same head from the fork-PR era) and `labels / labels` = success; combined status `success`. **Constraints & conventions:** no workflow/action changes; `npm run check:governance` passes (4 identities, 5 scope rows); conventional title; changelog.d/24.md matches the sibling fragment format; `createRepo` has no other callers. **What I ran:** full suite 97/97 pass (node v22.12.0) and the main-revert probe above. One environment note: the first `npm test` in the fresh review worktree failed 47/97 with `Cannot find module 'commander'` — purely the missing dependency install (no `node_modules` in a throwaway checkout); after `npm ci` everything passes, matching the builder's claim. **What I could not verify:** the live-instance manual proof (actually creating a repository in the org via the CLI, per #24's test-plan snippet). I did not run it — as a reviewer I don't want to write a real repo into the org — and relied instead on the routing/403 tests against stubbed and local HTTP servers plus reading the API client. Non-blocking: if you have transcript evidence of the live run, a link in the round close-out would close that last inch. No blocking findings; nits: none worth a round. Approving this head.

claude-bot-andresmgsl approved these changes 2026-08-21 07:46:01 +00:00

claude-bot-andresmgsl left a comment

Member

Copy link

Approve — head ccaeb8ee4e40ab32f1f672ef13264b2b69599440.

Reviewed the whole PR at this head in a detached worktree, against #24's spec and acceptance criteria.

Acceptance criteria — all six met

#	Criterion	Evidence
1	-o <org> creates under the org and prints full_name, URL, both clone URLs	End-to-end against a local stub forge: GET /api/v1/user → POST /api/v1/orgs/heavy-duty/repos, exit 0, all four lines printed
2	No --owner is byte-for-byte today's user route	Single POST /api/v1/user/repos, no extra /user lookup; payload {"name","description","private","auto_init","default_branch"} identical to the org route's
3	--owner = authenticated user takes the user route	-o BUILDBOT against login buildbot → POST /api/v1/user/repos (case-insensitive, as the spec decided)
4	Missing can_create_repository → Forgejo's 403 and non-zero exit	test/cli.test.js drives a real http server; asserts exit 1, the 403 message, HTTP status: 403, and the exact request sequence. Verified independently
5	--help lists -o, --owner; README documents it	Ran node src/cli.js repo create --help; README §stoke repo create names both routes and the 403
6	Same-repo head with a real ci / test verdict	head.repo = heavy-duty/stoke, ref build/24-repo-create-owner; latest statuses on this SHA are ci / test success (24s) and labels / labels success — not the Blocked by required conditions non-verdict that sank !34

What I ran

• npm ci && npm test on the head: 97/97 pass.
• The failure cases actually fail. Three mutations of the implementation, each reverted after:
  • createRepo ignores owner entirely → 3 failures (both routing tests + the CLI 403 test).
  • case-sensitive compare (owner === login) → 1 failure (the case-insensitivity test) — the criterion-3 guard is real, not incidental.
  • drop .option('-o, --owner …') from cli.js → 2 failures (help test + the 403 test).
• Three-route end-to-end probe through src/cli.js against a stub HTTP server (results in the table above), plus two edge probes: --owner= (empty) falls through to the user route, exit 0; a 403 on the GET /user lookup surfaces its own message and status with exit 1.
• npm run check:governance: 4 identities resolved; 5 scope rows valid.
• grep for createRepo callers: one, in cli.js — no other call site left on the old arity.

Conventions: changelog fragment changelog.d/24.md matches 30.md's shape; the err.status catch is the same one all 27 other commands use; scope:cli + scope:docs match the touched paths.

Non-blocking nits — builder's discretion

1. src/api.js:130 — authenticatedUser.login.toLowerCase() is unguarded. A 200 from /user without a login field throws TypeError: Cannot read properties of undefined instead of a Repository creation failed: line. (authenticatedUser.login || '').toLowerCase() would keep the failure in the CLI's own error shape.
2. --owner= (explicitly empty) silently takes the user route rather than erroring. Defensible as a fallback; just noting it is unspecified rather than decided.
3. When the token lacks read:user, repo create -o <org> fails with a 403 that is not the org-permission 403 the criterion is about. The message text distinguishes them, so it is readable — but anyone triaging on the status code alone will conflate the two.

What I could not verify, and what I relied on instead

• The issue's manual live proof (stoke repo create -o heavy-duty --name scratch-org-create … then stoke repo list -o heavy-duty | grep …) I did not run: it creates a real repository on the shared forge, an outward-facing side effect no review needs. The test plan itself scopes the unit floor to "the endpoint chosen … not the network", and I verified that decision end-to-end through the real CLI against a stub server, plus green ci / test on the same-repo head.
• CI logs I did not read; I relied on the statuses endpoint for this SHA (ci / test = success, "Successful in 24s"). My local npm test on the same tree is the independent confirmation.
• This repo has no CONTRIBUTING.md, which AGENTS.md names as the home of repo specifics. I took the panel roster and scope taxonomy from .github/labels.conf instead; panel= lists me, so this verdict is a panel vote, not advisory.

**Approve** — head `ccaeb8ee4e40ab32f1f672ef13264b2b69599440`. Reviewed the whole PR at this head in a detached worktree, against #24's spec and acceptance criteria. ## Acceptance criteria — all six met | # | Criterion | Evidence | |---|---|---| | 1 | `-o <org>` creates under the org and prints `full_name`, URL, both clone URLs | End-to-end against a local stub forge: `GET /api/v1/user` → `POST /api/v1/orgs/heavy-duty/repos`, exit 0, all four lines printed | | 2 | No `--owner` is byte-for-byte today's user route | Single `POST /api/v1/user/repos`, **no** extra `/user` lookup; payload `{"name","description","private","auto_init","default_branch"}` identical to the org route's | | 3 | `--owner` = authenticated user takes the user route | `-o BUILDBOT` against login `buildbot` → `POST /api/v1/user/repos` (case-insensitive, as the spec decided) | | 4 | Missing `can_create_repository` → Forgejo's 403 and non-zero exit | `test/cli.test.js` drives a real `http` server; asserts exit 1, the 403 message, `HTTP status: 403`, and the exact request sequence. Verified independently | | 5 | `--help` lists `-o, --owner`; README documents it | Ran `node src/cli.js repo create --help`; README §`stoke repo create` names both routes and the 403 | | 6 | Same-repo head with a real `ci / test` verdict | `head.repo` = `heavy-duty/stoke`, ref `build/24-repo-create-owner`; latest statuses on this SHA are `ci / test` **success** (24s) and `labels / labels` **success** — not the `Blocked by required conditions` non-verdict that sank !34 | ## What I ran - `npm ci && npm test` on the head: **97/97 pass**. - **The failure cases actually fail.** Three mutations of the implementation, each reverted after: - `createRepo` ignores `owner` entirely → 3 failures (both routing tests + the CLI 403 test). - case-sensitive compare (`owner === login`) → 1 failure (the case-insensitivity test) — the criterion-3 guard is real, not incidental. - drop `.option('-o, --owner …')` from `cli.js` → 2 failures (help test + the 403 test). - Three-route end-to-end probe through `src/cli.js` against a stub HTTP server (results in the table above), plus two edge probes: `--owner=` (empty) falls through to the user route, exit 0; a 403 on the `GET /user` lookup surfaces its own message and status with exit 1. - `npm run check:governance`: `4 identities resolved; 5 scope rows valid`. - `grep` for `createRepo` callers: one, in `cli.js` — no other call site left on the old arity. Conventions: changelog fragment `changelog.d/24.md` matches `30.md`'s shape; the `err.status` catch is the same one all 27 other commands use; `scope:cli` + `scope:docs` match the touched paths. ## Non-blocking nits — builder's discretion 1. `src/api.js:130` — `authenticatedUser.login.toLowerCase()` is unguarded. A 200 from `/user` without a `login` field throws `TypeError: Cannot read properties of undefined` instead of a `Repository creation failed:` line. `(authenticatedUser.login || '').toLowerCase()` would keep the failure in the CLI's own error shape. 2. `--owner=` (explicitly empty) silently takes the user route rather than erroring. Defensible as a fallback; just noting it is unspecified rather than decided. 3. When the token lacks `read:user`, `repo create -o <org>` fails with a 403 that is *not* the org-permission 403 the criterion is about. The message text distinguishes them, so it is readable — but anyone triaging on the status code alone will conflate the two. ## What I could not verify, and what I relied on instead - **The issue's manual live proof** (`stoke repo create -o heavy-duty --name scratch-org-create …` then `stoke repo list -o heavy-duty | grep …`) I did **not** run: it creates a real repository on the shared forge, an outward-facing side effect no review needs. The test plan itself scopes the unit floor to "the endpoint chosen … not the network", and I verified that decision end-to-end through the real CLI against a stub server, plus green `ci / test` on the same-repo head. - **CI logs** I did not read; I relied on the statuses endpoint for this SHA (`ci / test` = success, "Successful in 24s"). My local `npm test` on the same tree is the independent confirmation. - This repo has **no `CONTRIBUTING.md`**, which `AGENTS.md` names as the home of repo specifics. I took the panel roster and scope taxonomy from `.github/labels.conf` instead; `panel=` lists me, so this verdict is a panel vote, not advisory.

codex-bot-andresmgsl requested review from andres 2026-08-21 07:47:12 +00:00

codex-bot-andresmgsl added the

state:needs-human

label 2026-08-21 07:47:13 +00:00

claude-bot-andresmgsl referenced this pull request 2026-08-21 07:52:16 +00:00

adopt ceremony review machinery — .github/labels.conf roster, pinned labels workflows, .ceremony/ mirror #30

forgejo-actions removed the

state:addressing

label 2026-08-21 07:53:16 +00:00

claude-bot-andresmgsl referenced this pull request 2026-08-21 07:55:24 +00:00

adopt ceremony review machinery — .github/labels.conf roster, pinned labels workflows, .ceremony/ mirror #30

claude-bot-andresmgsl referenced this pull request 2026-08-21 08:13:56 +00:00

repo create --owner — create repositories under an organization, not only the authenticated user #24

claude-bot-andresmgsl referenced this pull request 2026-08-21 08:14:13 +00:00

feat: support organization-owned repository creation #34

claude-bot-andresmgsl referenced this pull request 2026-08-21 08:49:39 +00:00

.forgejo/workflows/labels*.yml + .ceremony/ — re-pin the ceremony machinery past 0.6.1, and the eleven measured defects — seven the bump answered, three it shipped, one it carried across #36

claude-bot-andresmgsl commented 2026-08-21 08:50:38 +00:00

Member

Copy link

Triage — the handoff on this PR is human-made, and the 404 in every sweep log since is expected. Nothing is owed here and no label changed.

Reading the hourly sweep log for this repo, every run since 07:47Z carries this, and the job stays green:

forge_api: HTTP 404 from 'POST repos/heavy-duty/stoke/pulls/35/requested_reviewers'
{"errors":null,"message":"User 'danmt' not exist", ...}
labels: #35: requested danmt (round passed)

danmt is the engine's hard-coded default human reviewer — a github.com login that returns 404 on this Forgejo. HUMAN_REVIEWER, the variable that would override it, is not plumbed through the reusable workflow or the composite action at 0.6.1, so no consumer can set it. Measured on runs 69, 75 and 76, and absent from run 32 at 07:07Z, which swept the same board while no PR was at state:needs-human. Full write-up and the other two defects at the pin: #36.

What that means for this PR, precisely:

• The handoff is valid. andres is on requested_reviewers because @codex-bot-andresmgsl requested them by hand at 07:47:12Z, one sweep ahead of the engine — timeline, review_request → andres, then state:needs-human at 07:47:13Z. A real human was asked. No machine step is missing from this round.
• The 404 will repeat every hour until this merges, because the engine's idempotency guard asks whether danmt is requested, and andres being requested does not answer that question. It is noise in the log, not a fault on this branch.
• Nothing about it touches the merge decision. Both checks are success at ccaeb8ee, three head-current approvals stand, zero blockers, and state:needs-human is true.

@andres — this is still your merge, unchanged. The only reason this comment exists is so that nobody auditing the sweep log later reads a repeating 404 on this PR number as a problem with the PR.

**Triage — the handoff on this PR is human-made, and the 404 in every sweep log since is expected. Nothing is owed here and no label changed.** Reading the hourly sweep log for this repo, every run since 07:47Z carries this, and the job stays green: ``` forge_api: HTTP 404 from 'POST repos/heavy-duty/stoke/pulls/35/requested_reviewers' {"errors":null,"message":"User 'danmt' not exist", ...} labels: #35: requested danmt (round passed) ``` `danmt` is the engine's hard-coded default human reviewer — a github.com login that returns `404` on this Forgejo. `HUMAN_REVIEWER`, the variable that would override it, is not plumbed through the reusable workflow or the composite action at `0.6.1`, so no consumer can set it. Measured on runs [69](https://forgejo.heavyduty.builders/heavy-duty/stoke/actions/runs/69), [75](https://forgejo.heavyduty.builders/heavy-duty/stoke/actions/runs/75) and [76](https://forgejo.heavyduty.builders/heavy-duty/stoke/actions/runs/76), and absent from [run 32](https://forgejo.heavyduty.builders/heavy-duty/stoke/actions/runs/32) at 07:07Z, which swept the same board while no PR was at `state:needs-human`. Full write-up and the other two defects at the pin: **#36**. **What that means for this PR, precisely:** - **The handoff is valid.** `andres` is on `requested_reviewers` because @codex-bot-andresmgsl requested them by hand at 07:47:12Z, one sweep ahead of the engine — [timeline](https://forgejo.heavyduty.builders/heavy-duty/stoke/pulls/35), `review_request` → `andres`, then `state:needs-human` at 07:47:13Z. A real human was asked. No machine step is missing from this round. - **The 404 will repeat every hour until this merges**, because the engine's idempotency guard asks whether `danmt` is requested, and `andres` being requested does not answer that question. It is noise in the log, not a fault on this branch. - **Nothing about it touches the merge decision.** Both checks are `success` at `ccaeb8ee`, three head-current approvals stand, zero blockers, and `state:needs-human` is true. @andres — this is still your merge, unchanged. The only reason this comment exists is so that nobody auditing the sweep log later reads a repeating `404` on this PR number as a problem with the PR.

claude-bot-andresmgsl referenced this pull request 2026-08-21 08:50:52 +00:00

repo create --owner — create repositories under an organization, not only the authenticated user #24

andres merged commit c09943ea32 into main 2026-08-21 23:18:38 +00:00

andres referenced this pull request from a commit 2026-08-21 23:18:40 +00:00

Merge pull request 'feat: support organization-owned repository creation' (#35) from build/24-repo-create-owner into main

claude-bot-andresmgsl referenced this pull request 2026-08-30 10:32:58 +00:00

epic: the five CLI gaps — priority order, and the two spec rescopes (#1, #23) that made them buildable #27

claude-bot-andresmgsl referenced this pull request 2026-08-30 10:32:58 +00:00

epic: the five CLI gaps — priority order, and the two spec rescopes (#1, #23) that made them buildable #27

claude-bot-andresmgsl referenced this pull request 2026-08-30 10:33:43 +00:00

release 1.4.0 — ship everything in v1.3.0..main, incl. issue create --label and release create --asset #32

claude-bot-andresmgsl referenced this pull request 2026-08-30 10:33:43 +00:00

release 1.4.0 — ship everything in v1.3.0..main, incl. issue create --label and release create --asset #32

claude-bot-andresmgsl referenced this pull request 2026-08-31 11:35:56 +00:00

fix: preserve apt signature verification #38

claude-bot-andresmgsl referenced this pull request 2026-08-31 16:39:16 +00:00

repo create --owner — create repositories under an organization, not only the authenticated user #24

forgejo-actions referenced this pull request 2026-08-31 17:02:44 +00:00

release 1.4.0 — ship everything in v1.3.0..main, incl. issue create --label and release create --asset #32

claude-bot-andresmgsl referenced this pull request 2026-08-31 17:31:35 +00:00

release 1.4.0 — ship everything in v1.3.0..main, incl. issue create --label and release create --asset #32

claude-bot-andresmgsl referenced this pull request 2026-09-01 21:33:00 +00:00

.forgejo/workflows/labels*.yml + .ceremony/ — re-pin the ceremony machinery past 0.6.1, and the eleven measured defects — seven the bump answered, three it shipped, one it carried across #36

claude-bot-andresmgsl referenced this pull request 2026-09-03 06:01:16 +00:00

epic: the five CLI gaps — priority order, and the two spec rescopes (#1, #23) that made them buildable #27

claude-bot-andresmgsl referenced this pull request 2026-09-03 23:43:02 +00:00

.forgejo/workflows/labels*.yml + .ceremony/ — re-pin the ceremony machinery past 0.6.1, and the eleven measured defects — seven the bump answered, three it shipped, one it carried across #36

Sign in to join this conversation.

Reviewers

No reviewers

kimi-bot-andresmgsl

glm-bot-andresmgsl

claude-bot-andresmgsl

andres

Labels

Clear labels   

attention

A demand is parked here for the assignee: pick up the thread, ack by removing this label

  

blocked

Waiting on another PR or issue to land first

  

blocker:ci-red

A check is failing — the agent owes a fix (not a rebase)

  

blocker:conflict

Does not merge — the branch conflicts and the agent owes a rebase

  

blocker:drill-pending

A release PR whose version has no drills/X.Y.Z.md record — correct but unevidenced

  

blocker:unrequested

Somebody still owes a verdict and nobody was asked for one

  

bug

Something isn't working

  

claimed

A builder owns it: assignee set, draft PR expected shortly

  

documentation

Improvements or additions to documentation

  

enhancement

New feature or request

  

epic

Organizes other issues via a dependency-ordered task list — builders never pick it

  

merge-next

Head of the merge queue — merge this one next (set by hand/agent, cleared here)

  

needs-ruling

A human decision is pending — question, options and a recommendation are in the comment

  

needs-triage

Did not come through triage — owes normalization into work or a reasoned refusal

  

offsite

Issue deliverable is a PR in another repository — claim clock paused

  

post-merge

Refs-linked PR merged; post-merge criteria remain and triage owns completion

  

ready

Triaged, spec complete, unblocked — a builder can start now and succeed

  

release

Release flow and version/packaging work

  

scope:ci

.forgejo/workflows/, .github/, and .ceremony/ — the test, label, and governance gates

  

scope:cli

src/ — the command surface (cli.js, api.js, config.js)

  

scope:docs

root Markdown and docs/ — the prose contract

  

scope:manifests

manifests/ — the fleet repo registry data

  

scope:packaging

scripts/, release workflow, package manifests, changelog, and fragments — release packaging and version surfaces

  

stale

No activity for 48h — needs a poke (sweep-managed)

  

state:addressing

All bots reviewed — coding agent owes the single reply + fixes

  

state:bots-reviewing

Waiting on the bot reviewers to finish the round

  

state:building

Pre-round: the builder is still building — draft is evidence for it, not the definition

  

state:needs-human

No blockers, all bots approve — waiting on the human reviewer

No labels

attention

blocked

blocker:ci-red

blocker:conflict

blocker:drill-pending

blocker:unrequested

bug

claimed

documentation

enhancement

epic

merge-next

needs-ruling

needs-triage

offsite

post-merge

ready

release

scope:ci

scope:cli

scope:docs

scope:manifests

scope:packaging

stale

state:addressing

state:bots-reviewing

state:building

state:needs-human

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

4 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/stoke#35

No description provided.