[goleary]

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 on github.repository == 'anomalyco/opencode'.
• The check-compliance job in pr-standards.yml, which applies the needs:compliance label 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-compliant job in compliance-close.yml and the check-compliance job in pr-standards.yml on github.repository == 'anomalyco/opencode'.
• Gates both jobs in duplicate-issues.yml, which also label needs:compliance and 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, run gh workflow disable compliance-close --repo replohq/replopencode.

^{Written for commit 11bbd00. Summary will update on new commits.}

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• No issue referenced. Please add Closes #<number> linking to the relevant issue.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🟡 Issue authors receive false closure warnings

Fork issues still receive needs:compliance warnings promising closure after two hours. The gated closer never performs that closure or removes the label.

Prompt for agents

The repository gate on .github/workflows/compliance-close.yml disables closure for both PRs and issues. However, .github/workflows/duplicate-issues.yml still labels non-compliant fork issues with needs:compliance and posts text promising automatic closure after two hours. Align the issue workflow with the fork behavior: either gate its compliance-label and warning paths for upstream only, or revise the fork's issue policy and messaging so labels and promised actions remain accurate. Consider how existing compliance labels and comments will be cleaned up after deployment.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[goleary]

Gated both jobs in duplicate-issues.yml on github.repository == 'anomalyco/opencode' in 11bbd00. Note this path is not reachable in the fork today: GitHub Issues are disabled on replohq/replopencode, so the issues: trigger never fires. The gate keeps behavior consistent if issues are enabled later.

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/compliance-close.yml">

<violation number="1" location=".github/workflows/compliance-close.yml:17">
P2: Gate the compliance-label and warning paths in `duplicate-issues.yml` as well. Otherwise fork issues still receive `needs:compliance` and a two-hour closure warning, while this gated job never closes them or removes the label.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Gate the compliance-label and warning paths in duplicate-issues.yml as well. Otherwise fork issues still receive needs:compliance and a two-hour closure warning, while this gated job never closes them or removes the label.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/compliance-close.yml, line 17:

<comment>Gate the compliance-label and warning paths in `duplicate-issues.yml` as well. Otherwise fork issues still receive `needs:compliance` and a two-hour closure warning, while this gated job never closes them or removes the label.</comment>

<file context>
@@ -13,6 +13,8 @@ permissions:
 jobs:
   close-non-compliant:
+    # Upstream-only: do not auto-close PRs/issues in the fork
+    if: github.repository == 'anomalyco/opencode'
     runs-on: ubuntu-latest
     steps:
</file context>

[goleary]

Done in 11bbd00: check-duplicates and recheck-compliance in duplicate-issues.yml now carry the same upstream-only gate. Issues are disabled in this fork so the workflow cannot currently fire, but the gate keeps the label and warning paths consistent with the disabled closer.