fix auto-generated CI rerun#1561
Conversation
|
Warning Review limit reached
More reviews will be available in 21 minutes and 1 second. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughGitHub Actions CI workflowの手動実行トリガーが追加され、自動生成ファイルのコミット検知・自動プッシュ・ワークフロー再実行・後続ジョブスキップ制御が実装されました。generate ジョブに必要な権限を付与し、auto_commit ステップでファイル差分をチェックしてコミット有無を出力、mod ジョブが自動コミット時にスキップされます。 Changes自動生成ファイルのコミット・再実行・後続ジョブ制御
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 @.github/workflows/main.yml:
- Around line 39-53: The workflow expands `${{ github.head_ref }}` directly into
shell commands (used in `git push origin HEAD:${{ github.head_ref }}` and `gh
workflow run main.yml --ref "${{ github.head_ref }}"`), creating a
command-injection risk; fix it by assigning the template value to a safe
environment variable (e.g., REF) and reference that var in the shell (export or
env: REF: ${{ github.head_ref }}), then use the quoted shell variable (`"$REF"`)
in the `git push` and `gh workflow run` invocations to prevent word-splitting
and injection.
🪄 Autofix (Beta)
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
Run ID: 4090e1d1-c164-47d6-9d6b-2b8f8e9e89ff
📒 Files selected for processing (1)
.github/workflows/main.yml
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1561 +/- ##
==========================================
+ Coverage 64.03% 64.10% +0.07%
==========================================
Files 27 27
Lines 4134 4134
==========================================
+ Hits 2647 2650 +3
+ Misses 1089 1087 -2
+ Partials 398 397 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Fix the auto-generated file commit flow in CI so that the generated commit is followed by a full CI run.
Background
The previous auto-commit used
[skip ci], so when GitHub Actions pushed regenerated files back to a PR branch, the follow-up commit did not run the full CI workflow. This could leave the PR without checks for the actual commit that would be merged.Changes
workflow_dispatchto the CI workflow.[skip ci]from the generated-files commit message.actions: writepermission for the generate job so it can trigger the workflow dispatch.Summary by CodeRabbit
改善