MrSphay/codex-agent-repository-kit
Template
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 5 Wiki Activity

Enforce Ubuntu runner policy

Browse Source
This commit is contained in:
MrSphay
2026-05-16 05:02:42 +02:00
parent a4245a1563
commit 2534640e54
11 changed files with 88 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
existing-project.md
View File

@@ -35,6 +35,8 @@ If local changes exist, do not overwrite them. Fetch or report the blocker befor
Conserve context tokens while inspecting: start with targeted searches and file lists, then read only files that affect the retrofit decision. Do not load generated folders, dependency folders, build outputs, or full logs unless they are directly relevant.
Treat `global-runner-1`, `global-runner-2`, and `global-runner-3` as the only supported build runners. Project builds, tests, audits, package jobs, installers, dependency setup, and releases must run on Gitea Ubuntu runners with `ubuntu-latest`, `ubuntu-24.04`, or `ubuntu-22.04`, not on the user's local machine. If tooling looks Windows-specific, use an open-source Linux-compatible workaround instead of adding a Windows runner.
Read:
```text
@@ -122,7 +124,7 @@ The default section divider is the rainbow line from `andreasbm/readme`, configu
If CI already exists:
- add missing audit/check steps,
- keep existing runner labels,
- replace unsupported runner labels with `ubuntu-latest`, `ubuntu-24.04`, or `ubuntu-22.04`,
- keep existing artifact names unless they are broken,
- avoid changing deployment behavior.
@@ -180,7 +182,8 @@ Use the stack-native audit command when possible:
Before final response:
- run `git diff --check`,
- run the smallest reliable verification command,
- run only lightweight local validation that does not install dependencies or create build artifacts,
- run the smallest reliable project verification command through Gitea Actions on a supported Ubuntu runner,
- if using Gitea Actions, poll the pushed workflow run until it reaches a terminal state; for private Gitea repositories on `https://git.wilkensxl.de`, use a locally set `GITEA_TOKEN` for read-only API status checks when available,
- if the pushed workflow fails or is cancelled, inspect the failing job/logs, fix in scope, push again, and repeat the workflow check loop; fixing and pushing is not a stopping point,
- list files changed,