ci(codeql): advanced setup — scope Swift autobuild to macos/** + weekly#1015
Conversation
Replace GitHub CodeQL default setup (which autobuilds the Swift macOS app on EVERY PR, no path filter — the 20M+ per-PR tax) with committed advanced workflows: - codeql.yml: python + javascript-typescript + actions on ubuntu, build-free, every PR/push + weekly. Cheap, unchanged coverage. - codeql-swift.yml: swift on macos-latest, autobuild, scoped to paths: macos/** (+ the workflow itself) + a weekly schedule — so the app still gets periodic security scanning but a pure-Python/QA PR no longer triggers the Swift autobuild. REQUIRES a one-time repo-owner toggle: Settings -> Code security and analysis -> Code scanning -> CodeQL analysis -> switch Default to Advanced (default + advanced cannot both run; codeql-action/init fails by design until default setup is disabled).
|
Warning Review limit reached
More reviews will be available in 49 minutes and 52 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Comment |
What & why
Analyze (swift)runs on every PR (including pure-Python/QA ones) because CodeQL is on GitHub default setup, which autobuilds the macOS Swift app per-language with no path filter — the slow/expensive job. This replaces default setup with committed advanced workflows that keep full language coverage but scope the Swift autobuild to when it actually matters.codeql.yml—python+javascript-typescript+actionsonubuntu-latest,build-mode: none(build-free), every PR/push to main + weekly. Same coverage, cheap.codeql-swift.yml—swiftonmacos-latest,build-mode: autobuild, scoped topaths: macos/**(+ the workflow file) and a weekly schedule — so the app still gets periodic scanning, but a Python/QA PR no longer pays the Swift-autobuild tax.Default CodeQL setup and advanced setup cannot both run —
codeql-action/initfails by design while default is enabled. After merging, flip:Until that toggle is flipped, these workflows will show red (init refuses). Recommend flipping it right at merge.
Coverage parity
Default setup analyzed:
actions,javascript-typescript,python,swift. This keeps all four — only the trigger forswiftchanges (scoped vs every-PR). No security coverage is dropped.