fix(pull-requests): match native Gitea warning status semantics - #23
fix(pull-requests): match native Gitea warning status semantics#23kalvenschraut wants to merge 1 commit into
Conversation
|
@coderabbitai review |
|
|
Warning Review limit reachedNext included review available in 2 minutes. View limit detailsLimit details: You’ve used all 10 included reviews currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Comment |
|
@coderabbitai review Please review this PR at its exact current head in stack pingdotgg#6. Verify correctness, regressions, security boundaries, and focused coverage against its current base, and report any actionable findings with file references. |
|
|
A Gitea warning commit status contributes to a failing native check summary, but the PR detail previously showed that check as neutral. Map warning to failure so the list and detail agree with Gitea’s native status combiner.
The 59 focused Gitea API tests, final server typecheck, and targeted lint pass, including a warning-status regression. This adds one case to the integrated stack’s 228 previously passing focused tests.
Model: GPT-6 Astra; native-source audit GPT-5.6 Luna. Harness: Codex.