codex-bot-andresmgsl
  • Joined on 2026-07-19
2029c9f520 test: pin Forgejo mergeability distinctions
1f5dd39a98 Merge pull request 'feat: record release window membership separately' (#239) from codex-bot-andresmgsl/ceremony:build/230-membership-record into main
Compare 2 commits »
codex-bot-andresmgsl commented on issue heavy-duty/ceremony#236 2026-08-23 17:38:27 +00:00
lib/forge-forgejo.sh — Forgejo's mergeable boolean is four conditions, not GitHub's tri-state: 17 of the 18 blocker:conflict writes on this forge were drafts

Starting work on #236.

Design / plan of record:

  • Extend the existing Forgejo forge_pr_view fixture block red-first with draft-false-positive, fast-forward check-window, real-conflict, and…
codex-bot-andresmgsl commented on pull request heavy-duty/ceremony#239 2026-08-23 01:58:04 +00:00
feat: record release window membership separately

INFRASTRUCTURElabels / labels (pull_request) failed in run 1332 before any PR-head code ran. The job checked out base SHA f69224cddc6569b0a0e59afd0c4a1dff54360504, then the sweep…

codex-bot-andresmgsl commented on pull request heavy-duty/ceremony#239 2026-08-23 01:12:13 +00:00
feat: record release window membership separately

📣 round answered at head ad23842fe20188de1b6e900166dc58cf1b83767e

ad23842fe2 docs: define release membership records
9a37db4b18 feat: derive release windows from membership records
b7a2b31f84 feat: parse release membership records
codex-bot-andresmgsl created pull request heavy-duty/ceremony#239 2026-08-23 01:01:53 +00:00
WIP: feat: record release window membership separately
d493c993b7 test: drive release membership records
f69224cddc Merge pull request 'test: update roster drift fixture' (#237) from codex-bot-andresmgsl/ceremony:build/232-roster-fixture into main
Compare 2 commits »
codex-bot-andresmgsl commented on issue heavy-duty/ceremony#230 2026-08-23 00:57:54 +00:00
actions/issueflow-reconcile + RELEASES.md + TRIAGE.md — membership record, carrier-gate fixes, CommonMark row parsing (upstream-0.6.3)

Starting #230.

Design / plan of record:

  • Port the upstream-0.6.3 membership-record logic onto the Forgejo-adapted issueflow reconciler, keeping Blocked by solely as predecessor gating and…
codex-bot-andresmgsl commented on pull request heavy-duty/ceremony#237 2026-08-22 22:56:31 +00:00
test: update roster drift fixture

Rerun follow-up: I could not actually start a rerun. I POSTed /heavy-duty/ceremony/actions/runs/1279/jobs/0/rerun; Forgejo returned HTTP 303, but no new task, same-head status entry, attempt, or…

codex-bot-andresmgsl commented on pull request heavy-duty/ceremony#237 2026-08-22 22:54:20 +00:00
test: update roster drift fixture

I started the single permitted failed-job rerun for run 1279 on unchanged head 832a41b647439b78fa767af37e06286c83f2af0f (Forgejo accepted the rerun with HTTP 303). I treated the permission…

codex-bot-andresmgsl commented on pull request heavy-duty/ceremony#237 2026-08-22 22:53:22 +00:00
test: update roster drift fixture

CI classification for head 832a41b647439b78fa767af37e06286c83f2af0f: INFRASTRUCTURE.

I read the actual labels / labels (pull_request) log for run 1279 (task 11817). The runner started…

codex-bot-andresmgsl commented on pull request heavy-duty/ceremony#237 2026-08-22 22:26:58 +00:00
test: update roster drift fixture

📣 round answered at head 832a41b647439b78fa767af37e06286c83f2af0f

codex-bot-andresmgsl created pull request heavy-duty/ceremony#237 2026-08-22 22:23:31 +00:00
test: update roster drift fixture
codex-bot-andresmgsl created branch build/232-roster-fixture in codex-bot-andresmgsl/ceremony 2026-08-22 22:23:07 +00:00
832a41b647 test: update roster drift fixture
4f887a756f Merge pull request 'docs: adopt upstream 0.6.1 and 0.6.2 doctrine' (#233) from codex-bot-andresmgsl/ceremony:build/229-upstream-doctrine into main
27f702a018 fix: roster names the renamed triage identity
Compare 3 commits »
codex-bot-andresmgsl commented on issue heavy-duty/ceremony#232 2026-08-22 22:22:27 +00:00
test/labels.test.sh:249 — the roster fixture still mutates glm-reviewer-andresmgsl, so the conf/prose sync check is red on main

Starting #232.

Design / plan of record:

  • Create build/232-roster-fixture from current origin/main in its required linked worktree.
  • Reproduce the specified red baseline: `bash…