ci.yml: update stale full-suite comment (Option B, #102) #106

Closed
Mark wants to merge 1 commit from fix/102-ci-full-suite-comment into main
Owner

Summary

Updates .forgejo/workflows/ci.yml to fix the stale full-suite comment. #95 was closed but the full suite still runs with continue-on-error: true and continues to fail; the tracking issue for those pre-existing failures is #102.

Rationale

This PR adopts Option B (update the comment to reference the tracking issue; keep the suite non-gating) rather than Option A (re-gating now by removing continue-on-error: true). Option B avoids regressing main on the pre-existing failures tracked in #102 (13 security, 15 integration, ~13 concurrent, performance) until that issue is resolved.

Follow-up

Once the tracking issue #102 is closed, the suite will be re-gated (Option A — remove continue-on-error: true from the full-suite and security-test steps).

References

  • Addresses the stale comment described in #102 (does not close #102 — the tracking issue stays open until the failures are fixed)
  • Related to #95 (the pre-existing failures that prompted the non-gating setup)
## Summary Updates `.forgejo/workflows/ci.yml` to fix the stale full-suite comment. #95 was closed but the full suite still runs with `continue-on-error: true` and continues to fail; the tracking issue for those pre-existing failures is #102. ## Rationale This PR adopts **Option B** (update the comment to reference the tracking issue; keep the suite non-gating) rather than Option A (re-gating now by removing `continue-on-error: true`). Option B avoids regressing `main` on the pre-existing failures tracked in #102 (13 security, 15 integration, ~13 concurrent, performance) until that issue is resolved. ## Follow-up Once the tracking issue #102 is closed, the suite will be re-gated (Option A — remove `continue-on-error: true` from the full-suite and security-test steps). ## References - Addresses the stale comment described in #102 (does not close #102 — the tracking issue stays open until the failures are fixed) - Related to #95 (the pre-existing failures that prompted the non-gating setup)
ci: update full-suite/security step comments to reference tracking issue #102
Some checks failed
CI / Backend Lint & Format (pull_request) Failing after 2m1s
CI / Golden Fixture Validation (pull_request) Has been skipped
CI / Backend Tests (pull_request) Has been skipped
CI / Backend Security Tests (pull_request) Has been skipped
CI / Frontend Lint (pull_request) Failing after 2m54s
CI / Frontend Tests (pull_request) Has been skipped
CI / Dependency Security Scan (pull_request) Has been skipped
CI / Frontend E2E Tests (pull_request) Has been skipped
CI / All Checks Passed (pull_request) Failing after 48s
3984b1d5bf
The full suite and security test steps are non-gating but their step names
still said 'until #95 is fixed'. #95 is closed; the pre-existing failures
are now tracked in #102 (13 security, 15 integration, ~13 concurrent,
performance). Update both step names to reference #102. No functional
change; continue-on-error: true retained on both steps.
Mark closed this pull request 2026-09-10 13:17:04 +00:00
Some checks failed
CI / Backend Lint & Format (pull_request) Failing after 2m1s
CI / Golden Fixture Validation (pull_request) Has been skipped
CI / Backend Tests (pull_request) Has been skipped
CI / Backend Security Tests (pull_request) Has been skipped
CI / Frontend Lint (pull_request) Failing after 2m54s
CI / Frontend Tests (pull_request) Has been skipped
CI / Dependency Security Scan (pull_request) Has been skipped
CI / Frontend E2E Tests (pull_request) Has been skipped
CI / All Checks Passed (pull_request) Failing after 48s

Pull request closed

Sign in to join this conversation.
No reviewers
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
Mark/osint-hub!106
No description provided.