Establish a Forgejo CI quality gate #9

Open
opened 2026-09-03 07:35:20 +00:00 by phg · 1 comment
Owner

Context

The repository has no Forgejo CI setup. This issue is intentionally blocked until the maintainer decides to adopt and configure Forgejo CI.

Acceptance criteria

  • A Forgejo runner and workflow are selected and documented.
  • CI installs the locked environment with uv.
  • CI runs pytest, Ruff lint, and Ruff format checks.
  • pytest-cov is installed and an explicit coverage threshold is chosen.
  • The README reports only checks that CI actually enforces.
Context The repository has no Forgejo CI setup. This issue is intentionally blocked until the maintainer decides to adopt and configure Forgejo CI. Acceptance criteria - A Forgejo runner and workflow are selected and documented. - CI installs the locked environment with uv. - CI runs pytest, Ruff lint, and Ruff format checks. - pytest-cov is installed and an explicit coverage threshold is chosen. - The README reports only checks that CI actually enforces.
phg added the
Status
Blocked
Kind/Testing
Priority
Medium
labels 2026-09-03 07:35:20 +00:00
Author
Owner

Blocked by: no Forgejo CI infrastructure or maintainer decision to adopt it yet. Unblock when: the maintainer explicitly decides to proceed and selects the runner and execution environment.

Blocked by: no Forgejo CI infrastructure or maintainer decision to adopt it yet. Unblock when: the maintainer explicitly decides to proceed and selects the runner and execution environment.
Sign in to join this conversation.
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: phg/hosts#9
No description provided.