ci(codeql): add workflow_dispatch + apply local prettier#73
Conversation
Two follow-ups to the workflow that landed in PR #72: 1. workflow_dispatch trigger so we can manually run scans against branches already behind the Enterprise PRs ruleset (the rule rejects the push that would otherwise trigger the scan — classic chicken-and-egg with no other escape hatch). 2. Single-quoted yaml string at line 71 to match the local Prettier config (the canonical version was double-quoted; this repo uses singleQuote in its prettier config).
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
This PR correctly adds workflow_dispatch trigger to enable manual CodeQL scans for branches behind the Enterprise PRs ruleset and updates YAML string formatting to match local Prettier configuration. Both changes function correctly with no defects detected.
Changes Reviewed:
- Addition of workflow_dispatch trigger with appropriate documentation (lines 28-31)
- Quote style update for consistency with Prettier configuration (line 75)
No blocking issues found. The changes are ready to merge.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
Two follow-ups to the workflow that landed in PR #72: