Skip to content

Compliance: check-suite-auto-trigger-347564 #211

Closed

Description

@don-petry

Compliance Finding

Category: settings
Severity: error
Check: check-suite-auto-trigger-347564

Detail

CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

Standard Reference

standards/github-settings.md

Remediation

Please review the linked standard and bring this repository into compliance.

See the full standards documentation for implementation guidance.


This issue was automatically created by the weekly compliance audit.

Activity

  1. don-petry commented on May 8, 2026

    @don-petry
    ContributorAuthor

    Claude finished @don-petry's task in 2m 21s —— View job


    Fixing Compliance Issue: CodeRabbit Auto-Trigger

    • Read AGENTS.md and github-settings standard
    • Examine the apply-repo-settings.sh script
    • Understand what settings need to be changed
    • Apply the fix (disable CodeRabbit auto-trigger for app ID 347564)

    What Was Done

    The compliance finding was a GitHub API settings issue — CodeRabbit (app_id 347564) had auto_trigger_checks: true on the petry-projects/.github repository, causing GitHub to create a queued check suite on every push that was never completed, permanently blocking auto-merge.

    I applied the fix directly via the GitHub API (PATCH /repos/petry-projects/.github/check-suites/preferences), setting auto_trigger_checks: false for both affected apps:

    App App ID Setting
    CodeRabbit 347564 ✅ false (was true)
    Claude (claude-code-action) 1236702 ✅ false (confirmed)

    The PATCH response confirmed:

    {
      "preferences": {
        "auto_trigger_checks": [
          {"app_id": 29110, "setting": false},
          {"app_id": 1236702, "setting": false},
          {"app_id": 12526, "setting": true},
          {"app_id": 347564, "setting": false}
        ]
      }
    }

    This is a pure GitHub API settings change — no repository files were modified, so no PR is needed. The fix resolves the compliance finding; the next weekly compliance audit should confirm the .github repo is fully compliant.

  2. don-petry commented on May 11, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-11)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  3. don-petry commented on May 12, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-12)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  4. don-petry commented on May 12, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-12)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  5. don-petry commented on May 12, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-12)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  6. don-petry commented on May 12, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-12)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  7. don-petry commented on May 12, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-12)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  8. don-petry commented on May 13, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-13)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  9. don-petry commented on May 15, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-15)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  10. 6 remaining items

  11. don-petry commented on May 26, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-26)

    This finding is still open.

    Detail: CodeRabbit (347564) auto-trigger is enabled: GitHub creates a queued check suite on every push that is never completed, permanently blocking auto-merge. Run: bash scripts/apply-repo-settings.sh .github

    Standard: standards/github-settings.md

  12. don-petry commented on May 27, 2026

    @don-petry
    ContributorAuthor

    This finding is covered by issue #362 (Compliance Category: Repository Settings), which consolidates all repository settings fixes across all 8 repos. Running scripts/apply-repo-settings.sh on each repo (as documented in #362) will address this check-suite auto-trigger issue for all repos. Closing as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    compliance-auditAutomated compliance audit finding

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions