feat(actions): org-level runner info - madt_actions only reaches repo runners #122

New issue

Closed

opened 2026-07-15 22:13:42 +00:00 by hexajon · 0 comments

hexajon commented

2026-07-15 22:13:42 +00:00

(Migrated from codeberg.org)

Checking "which runner picks up this repo's jobs" for an ORG-registered runner (sixfold_space, 2026-07-15) required falling back to the raw API passthrough:

madt_api_call GET /orgs/sixfold_space/actions/runners

because madt_actions action=runners (and runners_get/runners_delete/runners_token) is repo-scoped only. Runner administration commonly happens at the org level - repo-scoped listing shows nothing there, which reads as "no runner" when one exists.

Ask

Give the runner family (and plausibly secrets/variables, which Forgejo also scopes to orgs) an org form: e.g. an org= param on the existing actions, or accept a bare org in owner_repo= for these actions - pick whichever fits the existing scoping conventions.
CLI parity per naming-conventions.md, terse COMPARISON.md row, reference docs regenerated.

Acceptance

Org runners listable via a first-class madt_actions/CLI surface (labels, status, version included), no raw API needed.
Repo-scoped behavior unchanged.

Checking "which runner picks up this repo's jobs" for an ORG-registered runner (sixfold_space, 2026-07-15) required falling back to the raw API passthrough: madt_api_call GET /orgs/sixfold_space/actions/runners because `madt_actions action=runners` (and runners_get/runners_delete/runners_token) is repo-scoped only. Runner administration commonly happens at the org level - repo-scoped listing shows nothing there, which reads as "no runner" when one exists. ## Ask - Give the runner family (and plausibly secrets/variables, which Forgejo also scopes to orgs) an org form: e.g. an `org=` param on the existing actions, or accept a bare org in `owner_repo=` for these actions - pick whichever fits the existing scoping conventions. - CLI parity per naming-conventions.md, terse COMPARISON.md row, reference docs regenerated. ## Acceptance - Org runners listable via a first-class madt_actions/CLI surface (labels, status, version included), no raw API needed. - Repo-scoped behavior unchanged.

No milestone

No project

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

sixfold-space/madtea#122

No description provided.

Rows
Columns