Repository navigation
Conversation
|
Warning Review limit reached
More reviews will be available in 58 minutes and 43 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@don-petry — PR is ready for review and merge. Single change: removes drift |
There was a problem hiding this comment.
Pull request overview
Removes the repository’s custom CodeQL GitHub Actions workflow to eliminate drift from the org standard, relying instead on GitHub-managed CodeQL Default Setup.
Changes:
- Deleted
.github/workflows/codeql.yml(custom CodeQL workflow that analyzed onlyactions).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Auto-rebase failed — merge conflict — this branch has conflicts with Please resolve the conflicts and push: |
Per org standard §2 (standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup), CodeQL scanning must use GitHub-managed default setup — not a per-repo workflow file. The default setup is confirmed configured (state=configured, languages: actions, go, javascript, typescript) via the code-scanning API. The stray codeql.yml scanned only the `actions` ecosystem and creates a duplicate analysis alongside the default setup, wasting CI minutes. Removing it leaves the default setup as the sole CodeQL analysis path, which auto-detects all supported languages on the default branch. Closes #109 Co-authored-by: don-petry <don-petry@users.noreply.github.com>
0754ae0 to
f47edaa
Compare
|
|
@dev-lead - please fix this PR |
Dev-Lead — fix-bot-comment (applied)Changes committed and pushed. |
|
|
Closing due to merge conflict that cannot be auto-rebased. Re-implementing from fresh main via dev-lead. |
Pull request was closed



Summary
.github/workflows/codeql.yml, which is drift per org standard §2 (ci-standards.md#2)state=configured, languages:actions,go,javascript,typescript,query_suite: default)gh api -X PATCH repos/petry-projects/broodly/code-scanning/default-setup -F state=configured -F query_suite=defaultas part of remediationWhy the compliance finding keeps recurring
The audit's
GH_TOKENdoes not have thesecurity_eventsread scope needed to callGET /repos/petry-projects/broodly/code-scanning/default-setup. It receives a 403, which the script interprets as "not configured". This is an audit-bot permissions issue, not a repo configuration issue — the default setup is genuinely configured.Removing the drift
codeql.ymleliminates thestray-codeql-workflowcheck, and should eliminate the duplicate CodeQL analysis. Thecodeql-default-setup-not-configuredfinding will stop once the audit bot's token is granted the necessary scope.Test plan
state=configuredvia API before and aftercodeql.ymlwas only scanningactions(already covered by default setup)codeql.ymlCloses #109
Generated with Claude Code