Nothing runs the project's checks except the person who remembers to #14

New Issue

2026-09-21T07:18:05Z

cgalo5758 commented

2026-09-21 07:18:05 +00:00

The question

The build, the vet pass and the project lint run locally, as the first step of the test target. A workflow that ran them on the forge on every push and pull request was written and withdrawn the same day, along with the requirement that said the lint runs there, because what continuous integration would be worth here had not been worked out. So: does this project run its checks automatically, what does it run, and where?

What depends on the answer

Whether a contributor who is not the person merging gets an answer about their change without being asked, and whether the lint rules can be treated as enforced. Facts that bear on it: the forge hosts an actions service, which answered for this repository with no workflows configured; whether a runner is available to it was never checked; and another automation service already runs in the infrastructure this project is deployed on, so a second one needs a reason.

Options known so far

Workflows on the forge, if a runner exists: build, vet and lint on push and on pull request, with the test stack left out until it can run there.
The existing automation service, with the project's checks added to it.
Nothing automatic, with the local target named as the gate in the contributing guide and the rule that it runs before a merge.

Decided when

The project says where its checks run and which ones, the contributing guide matches, and the design system no longer implies a gate that does not exist.

Migrated from status/issues.md at b7a0e15

## The question The build, the vet pass and the project lint run locally, as the first step of the test target. A workflow that ran them on the forge on every push and pull request was written and withdrawn the same day, along with the requirement that said the lint runs there, because what continuous integration would be worth here had not been worked out. So: does this project run its checks automatically, what does it run, and where? ## What depends on the answer Whether a contributor who is not the person merging gets an answer about their change without being asked, and whether the lint rules can be treated as enforced. Facts that bear on it: the forge hosts an actions service, which answered for this repository with no workflows configured; whether a runner is available to it was never checked; and another automation service already runs in the infrastructure this project is deployed on, so a second one needs a reason. ## Options known so far - Workflows on the forge, if a runner exists: build, vet and lint on push and on pull request, with the test stack left out until it can run there. - The existing automation service, with the project's checks added to it. - Nothing automatic, with the local target named as the gate in the contributing guide and the rule that it runs before a merge. ## Decided when The project says where its checks run and which ones, the contributing guide matches, and the design system no longer implies a gate that does not exist. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/testing area/meta labels 2026-09-21 07:18:05 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#14