chore(ci): disable needs:compliance auto-close in the fork
What does this PR do?
Stops the inherited upstream compliance automation from auto-closing PRs in this fork. A PR was closed by github-actions after the 2-hour needs:compliance window today.
compliance-close.yml(scheduled every 30 min, closes labeled PRs/issues after 2 hours) is now gated ongithub.repository == 'anomalyco/opencode'.- The
check-compliancejob inpr-standards.yml, which applies theneeds:compliancelabel and posts the 2-hour warning, gets the same gate.
This matches how the fork already handles other upstream-only workflows (deploy, publish, stats). The title-format and linked-issue checks in pr-standards.yml are unchanged.
Note: the scheduled job runs from the default branch, so it keeps firing until this merges to dev. To stop it right away: gh workflow disable compliance-close --repo replohq/replopencode.
Type of change
- Bug fix
- New feature
- Other: CI configuration
How did you verify your code works?
Workflow-only change; the if: gate uses the exact expression already present on stats.yml and publish.yml in this repo.
Checklist
- I have tested this locally
- I have not included unrelated changes
Issue for this PR
N/A
š¤ Generated with Claude Code
Summary by cubic
Stops the inherited upstream compliance automation from auto-closing PRs and issues in this fork, after a PR was closed by github-actions following the 2-hour needs:compliance window.
- Gates the
close-non-compliantjob incompliance-close.ymland thecheck-compliancejob inpr-standards.ymlongithub.repository == 'anomalyco/opencode'. - Gates both jobs in
duplicate-issues.yml, which also labelneeds:complianceand post the 2-hour warning. - Matches how the fork already handles other upstream-only workflows; title-format and linked-issue checks are unchanged.
- The scheduled job keeps firing until this merges to
dev; to stop it right away, rungh workflow disable compliance-close --repo replohq/replopencode.