FIRSTMATE-32: disable CI/CD triggers for now (Actions off, firstmate-ng active) #50

Merged

john merged 1 commit from fm/fm-ci-disable into main 2026-10-19 05:08:11 +00:00

Conversation 0 Commits 1 Files changed 1 +8 -4

john commented 2026-10-19 05:06:20 +00:00

Owner

Copy link

Story: FIRSTMATE-32 - disable firstmate CI/CD triggers

What was wrong

The forge CI fan-out on this fork was eating hundreds of runner-hours. The
active development surface has moved to firstmate-ng, so this repo's full
push/PR CI spend is not worth the runner cost right now.

What changed

.forgejo/workflows/ci.yml only:

• The on: triggers are replaced: push (branches: main) and
  pull_request (branches: main) are removed; the workflow now triggers on
  workflow_dispatch only.
• A header comment above on: records the why: captain order 2026-10-19,
  CI/CD paused because the fan-out was consuming hundreds of runner-hours on
  the fork while work moves to firstmate-ng; re-enable by restoring the
  triggers in one revert; Forge Actions are also disabled repo-wide via the
  forge settings, so the in-repo change makes the disable durable against an
  accidental settings re-enable.

No job definitions, no timeout policy, and no other file changed. The
upstream .github/workflows/ mirror stays byte-identical. The concurrency
grouping block is left in place so the restore is a clean revert; it is inert
while the only trigger is manual.

Guard tests

• bash tests/fm-forge-workflow.test.sh (forge workflow guard): green.
  The guard test asserts jobs, timeout tiers, runners, matrices, and
  concurrency behavior, not the trigger set, so it needed no update.
• bash tests/fm-ci-workflow.test.sh (upstream GitHub workflow guard):
  green (ran in a container with ruby; .github/workflows/ci.yml is
  untouched).

Stays open

• Re-enable path: one revert of this commit restores the original
  push/pull_request triggers. Forge Actions are also disabled repo-wide via
  settings, so full CI needs both the settings re-enable and (optionally)
  this revert.
• firstmate-ng is the active surface: this repo's CI pause is a cost
  decision for now, not a permanent deletion; the jobs are preserved as-is.

Checks

Forge CI will not run on this PR: Actions are disabled repo-wide on
git.pyr0.dev (see above), so there are no checks to wait for. The guard
tests were run locally and are green.

**Story:** FIRSTMATE-32 - disable firstmate CI/CD triggers ## What was wrong The forge CI fan-out on this fork was eating hundreds of runner-hours. The active development surface has moved to firstmate-ng, so this repo's full push/PR CI spend is not worth the runner cost right now. ## What changed `.forgejo/workflows/ci.yml` only: - The `on:` triggers are replaced: `push` (branches: main) and `pull_request` (branches: main) are removed; the workflow now triggers on `workflow_dispatch` only. - A header comment above `on:` records the why: captain order 2026-10-19, CI/CD paused because the fan-out was consuming hundreds of runner-hours on the fork while work moves to firstmate-ng; re-enable by restoring the triggers in one revert; Forge Actions are also disabled repo-wide via the forge settings, so the in-repo change makes the disable durable against an accidental settings re-enable. No job definitions, no timeout policy, and no other file changed. The upstream `.github/workflows/` mirror stays byte-identical. The concurrency grouping block is left in place so the restore is a clean revert; it is inert while the only trigger is manual. ## Guard tests - `bash tests/fm-forge-workflow.test.sh` (forge workflow guard): **green**. The guard test asserts jobs, timeout tiers, runners, matrices, and concurrency behavior, not the trigger set, so it needed no update. - `bash tests/fm-ci-workflow.test.sh` (upstream GitHub workflow guard): **green** (ran in a container with ruby; `.github/workflows/ci.yml` is untouched). ## Stays open - **Re-enable path:** one revert of this commit restores the original push/pull_request triggers. Forge Actions are also disabled repo-wide via settings, so full CI needs both the settings re-enable and (optionally) this revert. - **firstmate-ng is the active surface:** this repo's CI pause is a cost decision for now, not a permanent deletion; the jobs are preserved as-is. ## Checks Forge CI will not run on this PR: Actions are disabled repo-wide on git.pyr0.dev (see above), so there are no checks to wait for. The guard tests were run locally and are green.

john added 1 commit 2026-10-19 05:06:20 +00:00

FIRSTMATE-32: disable CI/CD triggers for now (Actions off, firstmate-ng active) ... 92286d4860

Replace the forge workflow's push/pull_request triggers with
workflow_dispatch only so an accidental repo-settings re-enable cannot
silently restart the full fan-out, which was eating hundreds of
runner-hours on this fork while the active work has moved to
firstmate-ng. Job definitions, timeout policy, and the upstream
.github/workflows mirror are untouched; re-enable by reverting this
change.

john merged commit 1049ed33f2 into main 2026-10-19 05:08:11 +00:00

john referenced this pull request from a commit 2026-10-19 05:08:12 +00:00

FIRSTMATE-32: disable CI/CD triggers for now (Actions off, firstmate-ng active) (#50)

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

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

john/firstmate!50

No description provided.