docs(lane1): verify CodeQL re-remove fix already open in PR #235 (fresh main) - #242
Conversation
…sh main) The CodeQL analyze job regression on main (re-added by merge 410f3e6, silently SKIPPING on every trigger) is real, but the correct fix already exists as open, green, mergeable PR #235, based on current origin/main head ccfbd4b. This lane intentionally did not re-implement the fix: the repo's pr-duplicate-guard exists because duplicate same-fix PRs became a fleet failure mode. Evidence report only, following the PR #183 precedent. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 58 minutes Limit details: You’ve used the included review currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (1)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/settings/billing. Comment |
What this is
Lane-1 verification evidence for the "[unreviewed-by-opus] PR #82's CodeQL
analyze now RUNS on every trigger but FAILS at the final step" item.
Finding: the CodeQL analyze-job regression on main is real — merge
410f3e66(2026-08-19) re-added.github/workflows/codeql.ymlwith theprivate-repo gate, so the job silently reports green "SKIPPED" on every
push/PR/schedule, contradicting the documented PR #122 decision that this
nonfunctional workflow stay removed (no GHAS entitlement on this plan;
npm audit --audit-level=highin the requiredrepo-checksjob is thedeliberate substitute).
But the fix already exists: open PR #235
(
fix/lane1-codeql-private-repo-gate-reremove-20260821, commitda110c8) deletescodeql.ymland records the re-addition inREADME.md— and it is basedon the exact current origin/main HEAD (
ccfbd4bis da110c8's parent),green (
repo-checks,duplicate-guard, CodeRabbit all SUCCESS), andmergeable.
This lane deliberately did NOT re-implement the fix: the repo's own
pr-duplicate-guardflags >= 80% shared-file-coverage duplicates, andduplicate same-fix PR pairs are a documented fleet failure mode. This PR
carries the verification evidence only, following the PR #183 precedent.
Files changed
.lane/reports/docs-lane1-codeql-reremove-verify-20260821.md— evidence reportRecommendation
Merge PR #235 to restore the documented no-CodeQL state on main; the
re-enable path (set
ENABLE_PRIVATE_CODEQL=1once GHAS is provisioned)stays unchanged in
.github/workflows/README.md.