feat: scheduled automerge + resume generator workflow#109
Conversation
Replace pull_request-triggered automerge with nightly schedule + manual dispatch. Runs with full secret access, finds eligible dependabot/release-please PRs, checks CI status, approves and merges. Add resume.yml workflow that regenerates PDF/DOCX when resume.json or generator scripts change in a PR, commits back, and comments. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Warning Rate limit exceeded
⌛ 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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.
Summary
This PR refactors the automerge workflow to run on a schedule instead of PR events, and adds a new resume generator workflow. The approach solves the secret access and self-approval issues mentioned in the PR description.
Critical Issues Found
Automerge workflow:
- CI check validation uses brittle string parsing that may silently fail when
gh pr checksencounters errors, potentially allowing PRs with failing checks to merge - Missing error handling for
gh pr listcommand failures could cause jq parsing errors or silent failures
Resume generator workflow:
- Missing file existence checks before
git diffwill cause workflow failure on first run or if files are deleted - No error handling for resume generation failures could result in committing corrupted or incomplete files
All identified issues have blocking severity and must be fixed before merge to prevent workflow failures and incorrect automerge behavior.
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.
Use structured JSON output and jq for CI check parsing instead of brittle grep. Add error handling for API failures. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
pull_requesttrigger with nightlyschedule(6 AM UTC) +workflow_dispatch. Runs on default branch context with full secret access — no more emptyCI_GITHUB_TOKENon dependabot PRs, no more self-approval failures on release-please PRs.resume.jsonor generator scripts. Regenerates PDF/DOCX, commits back to PR branch if changed, comments on PR.What was broken
Automerge on
pull_requestevent had two fatal issues:CI_GITHUB_TOKENwas empty →ghCLI failedTest plan
workflow_dispatchto process the 8 stuck dependabot PRs🤖 Generated with Claude Code