docs: require manual issue approval
Some checks failed
CI / test (push) Has been cancelled
CI / test (pull_request) Has been cancelled

This commit is contained in:
Christian Meyer
2026-08-31 10:53:21 +02:00
parent 078c22b5e0
commit cf1d8acb45

View File

@@ -5,13 +5,16 @@ Laravel production database and does not merge changes automatically.
## Workflow ## Workflow
1. LAI creates one Gitea issue for a wrong-answer report and labels it `ai:queued`. 1. LAI creates one unlabeled Gitea issue for a wrong-answer report.
2. This worker replaces the label with `ai:running`, clones `main`, and creates `ai/issue-N`. 2. An administrator reviews it and explicitly applies `ai:queued`, either through the LAI admin dashboard or directly in Gitea.
3. mini-SWE-agent 2.4.6 implements the issue in a credential-free, unprivileged command environment. 3. This worker replaces the label with `ai:running`, clones `main`, and creates `ai/issue-N`.
4. The worker rejects protected paths, symlinks, empty patches, and oversized diffs. 4. mini-SWE-agent 2.4.6 implements the issue in a credential-free, unprivileged command environment.
5. Deterministic setup and test commands run with isolated test database credentials. 5. The worker rejects protected paths, symlinks, empty patches, and oversized diffs.
6. A pull request containing `Fixes #N`, the original problem, changed files, and checks is opened. 6. Deterministic setup and test commands run with isolated test database credentials.
7. The issue is labeled `ai:ready` or `ai:failed` and receives a status comment. 7. A pull request containing `Fixes #N`, the original problem, changed files, and checks is opened.
8. The issue is labeled `ai:ready` or `ai:failed` and receives a status comment.
Normal reports are never selected automatically. The manual `ai:queued` label is the explicit approval and the only worker trigger.
Human review and merge are always required. Human review and merge are always required.