chore(ci): consolidate immutable CodeQL action pins - #145
Conversation
|
Warning Review limit reached
Next review available in: 22 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughCodeQL 워크플로의 checkout 및 CodeQL 액션을 불변 커밋으로 갱신했습니다. checkout 자격 증명 지속을 비활성화했습니다. 보안 계약 테스트와 운영 문서를 추가했습니다. ChangesCodeQL 워크플로 보안
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
@opencode-agent review Please review exact current head |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/test_codeql_workflow_security.py`:
- Around line 21-36: Update the security workflow test around the existing
checkout and CodeQL assertions to parse the YAML and select the checkout, init,
and analyze steps structurally. Compare each step’s uses value directly against
its expected SHA, assert checkout’s with.persist-credentials is boolean false,
and assert analyze retains its if: ${{ false }} condition and the workflow’s
read-only permissions.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 0eb7730e-a6a3-40f8-817c-0782e2ad907a
📒 Files selected for processing (4)
.github/workflows/codeql.ymlCHANGELOG.mddocs/doctoring/codeql-action-pin-consolidation.mdtests/test_codeql_workflow_security.py
|
@opencode-agent review-only request for exact current head |
Purpose
Consolidate three overlapping dependency updates into one current-main, test-first supply-chain change for the repository's manual CodeQL marker workflow.
Test-first history
44ea2827947d7cdde0063488f8da2ca50a373459.496474275cb3fdb8f8a54dee02a4767acdb0b8f8.d890ddb71f931a2a8d07d1260caea8086e6fd0c3.The permanent test was committed before the workflow implementation. It requires the reviewed full-length action pins and checkout credential boundary and fails against the protected-base workflow.
Change
actions/checkoutv7.0.1 to3d3c42e5aac5ba805825da76410c181273ba90b1;persist-credentials: falseon the checkout step;github/codeql-action/initand the disabled documentation-onlyanalyzemarker to v4.37.6 commit5595ccaf912efad79be6eef63a5619ff05969be3;The official v4.37.6 tag resolves exactly to the pinned CodeQL commit. No tag, branch, reviewer identity, credential name, security threshold, or branch protection is changed.
Supersession
This current-main replacement fully supersedes:
persist-credentials: false;Those predecessor PRs should be closed after this replacement is confirmed to carry their complete valid scope. No predecessor-head check or approval is reused.
Exact-head merge gate
Merge only after the exact current head passes the complete repository tests, all required security and policy checks, current-head automated review, zero unresolved actionable threads, and a qualifying independent non-last-pusher approval. Pending, queued, skipped-required, cancelled, absent, failed, stale-head, status-only, or author-only evidence is not success.
Summary by CodeRabbit
보안 개선
문서