Skip to content

ci(codeql): run CodeQL on every trigger (drop private-repo gate) - #82

Closed
nish3451 wants to merge 1 commit into
mainfrom
fix/codeql-private-repo-gate
Closed

ci(codeql): run CodeQL on every trigger (drop private-repo gate)#82
nish3451 wants to merge 1 commit into
mainfrom
fix/codeql-private-repo-gate

Conversation

@nish3451

Copy link
Copy Markdown
Collaborator

Problem

The CodeQL analyze job has skipped on every run since the repo baseline:

if: ${{ github.event.repository.private == false || vars.ENABLE_PRIVATE_CODEQL == '1' }}

tinystudio-in is a private repo, so repository.private == false is false, and the ENABLE_PRIVATE_CODEQL repo variable is unset (verified: the variable is referenced nowhere else in the repo, and no workflow run ever executed the job). Both gate conditions are false on every run — CodeQL security analysis never runs.

Fix

Remove the job-level if gate entirely, with a comment explaining why (so the gate is not accidentally re-added). The job now runs on every trigger: pull_request, push to main/codex/**, the weekly Monday 03:23 schedule, and workflow_dispatch.

Verification

  • Repo visibility: unauthenticated GET /repos/nish3451/tinystudio-in returns 404 (private).
  • ENABLE_PRIVATE_CODEQL appears only in codeql.yml (git log -S across all branches: introduced with baseline commit a8be36c, never set as a repo variable).
  • YAML parses cleanly (PyYAML safe_load).
  • A CodeQL run should now start on this PR.

The analyze job's if-condition required the repo to be public or the
ENABLE_PRIVATE_CODEQL repo variable to equal '1'. tinystudio-in is
private and the variable is unset, so CodeQL security analysis never
ran. Remove the gate so the job runs on every trigger (PR, push to
main/codex/**, weekly schedule, workflow_dispatch).

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 92de1e74-05b9-4f16-8f00-d22933536e49

📥 Commits

Reviewing files that changed from the base of the PR and between 45ef63b and 93364e3.

📒 Files selected for processing (1)
  • .github/workflows/codeql.yml

Comment @coderabbitai help to get the list of available commands.

@nish3451

Copy link
Copy Markdown
Collaborator Author

Superseded by #89 (same gate drop + the missing actions: read permission that fixes the Resource not accessible by integration failure in the final analyze step). Closing this one so the fix lands as a single verifiable PR.

@nish3451

Copy link
Copy Markdown
Collaborator Author

Closed as superseded by #89 — the fix now includes the permission change that makes the analyze step finish successfully.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant