Skip to content

chore(ci): disable needs:compliance auto-close in the fork #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
goleary merged 2 commits into from
Sep 2, 2026
Merged

chore(ci): disable needs:compliance auto-close in the fork #36

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c690ee1
ci: disable needs:compliance auto-close in the fork
goleary Sep 2, 2026
11bbd00
ci: gate issue compliance labeling on upstream repo too
goleary Sep 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/compliance-close.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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'

@devin-ai-integration devin-ai-integration Bot Sep 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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.
Devin Review

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

@goleary goleary Sep 2, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 cubic-dev-ai Bot Sep 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 goleary Sep 2, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

runs-on: ubuntu-latest
steps:
- name: Close non-compliant issues and PRs after 2 hours
Expand Down
6 changes: 4 additions & 2 deletions .github/workflows/duplicate-issues.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ on:

jobs:
check-duplicates:
if: github.event.action == 'opened'
# Upstream-only: labels needs:compliance and warns of the 2-hour auto-close
if: github.repository == 'anomalyco/opencode' && github.event.action == 'opened'
runs-on: blacksmith-4vcpu-ubuntu-2404
permissions:
contents: read
Expand Down Expand Up @@ -140,7 +141,8 @@ jobs:
Remember: post at most ONE comment combining all findings. If everything is fine, post nothing."

recheck-compliance:
if: github.event.action == 'edited' && contains(github.event.issue.labels.*.name, 'needs:compliance')
# Upstream-only: see check-duplicates
if: github.repository == 'anomalyco/opencode' && github.event.action == 'edited' && contains(github.event.issue.labels.*.name, 'needs:compliance')
runs-on: blacksmith-4vcpu-ubuntu-2404
permissions:
contents: read
Expand Down
2 changes: 2 additions & 0 deletions .github/workflows/pr-standards.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,8 @@ jobs:
console.log('PR meets all standards');

check-compliance:
# Upstream-only: this labels needs:compliance and warns of the 2-hour auto-close
if: github.repository == 'anomalyco/opencode'
runs-on: ubuntu-latest
permissions:
contents: read
Expand Down
Loading