ci.yml: update stale full-suite comment (Option B, #102) #106
No reviewers
Labels
No labels
agentic-osint
audit
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:preflight
blocked:verify-failed
bug
chore
deferred
enhancement
feature-request
in-progress
lint-baseline
lint-cleanup
needs-decompose
needs-triage
performance
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/osint-hub!106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/102-ci-full-suite-comment"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Updates
.forgejo/workflows/ci.ymlto fix the stale full-suite comment. #95 was closed but the full suite still runs withcontinue-on-error: trueand 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 regressingmainon 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: truefrom the full-suite and security-test steps).References
Pull request closed