Grey.ooo/agent-standards
Watch
2
0
Fork
You've already forked agent-standards
 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Document Forgejo's per-job CI rerun button #33

Merged
geusebio merged 1 commit from docs/forgejo-per-job-rerun into main 2026-08-25 19:53:06 +00:00
Conversation 0 Commits 1 Files changed 1 +15
geusebio commented 2026-08-25 19:40:58 +00:00
Owner
Copy link

What

Documents a Forgejo capability found while chasing a red E2E job on
Someones.Computer#1126: every job in a run's sidebar carries its own
rerun icon (revealed on hover, just before its duration), separate
from the existing Re-run all jobs button. It re-runs only that job,
and lets whatever's downstream of it (e.g. Ship behind E2E)
re-evaluate once it finishes — no new commit, and no re-running work
that already passed.

Why

VCS.md already covers watching CI (tea pulls --fields ci's dropped
rows, the commit-statuses cross-check) but had nothing on re-running a
red job short of a new commit or the whole-run button. Neither the API
nor tea can trigger a re-run at all on this Forgejo, so the run page
is the only route — worth a session knowing both granularities exist.

Verified

Pure docs change — docs/Topics/VCS.md only. Ran the platform repo's
own bin/lint-markdown.sh against this file as a sanity check: two
pre-existing findings elsewhere in the file (unrelated, untouched by
this diff), nothing near the new section.

## What Documents a Forgejo capability found while chasing a red E2E job on Someones.Computer#1126: every job in a run's sidebar carries its own rerun icon (revealed on hover, just before its duration), separate from the existing `Re-run all jobs` button. It re-runs only that job, and lets whatever's downstream of it (e.g. `Ship` behind `E2E`) re-evaluate once it finishes — no new commit, and no re-running work that already passed. ## Why VCS.md already covers watching CI (`tea pulls --fields ci`'s dropped rows, the commit-statuses cross-check) but had nothing on re-running a red job short of a new commit or the whole-run button. Neither the API nor `tea` can trigger a re-run at all on this Forgejo, so the run page is the only route — worth a session knowing both granularities exist. ## Verified Pure docs change — `docs/Topics/VCS.md` only. Ran the platform repo's own `bin/lint-markdown.sh` against this file as a sanity check: two pre-existing findings elsewhere in the file (unrelated, untouched by this diff), nothing near the new section.
Neither the API nor tea can trigger a re-run on this Forgejo at all,
but the run page can, at two granularities most sessions only know
the coarser of: every job in the run's sidebar carries its own
rerun icon, re-running just that job (and letting what's downstream
of it re-evaluate) instead of the whole pipeline. Needs an
authenticated page — Claude-in-Chrome, not the unauthenticated
in-app Browser pane.
geusebio deleted branch docs/forgejo-per-job-rerun 2026-08-25 19:53:07 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
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
Grey.ooo/agent-standards!33
No description provided.