ci: auto-sync prompt artifacts from upstream prompts.yml#137
Conversation
|
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: 31 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 Run ID: 📒 Files selected for processing (1)
✨ 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 |
Greptile SummaryThis PR adds an automated prompt artifact sync workflow. The main changes are:
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (1): Last reviewed commit: "ci: add bot to sync prompt artifacts fro..." | Re-trigger Greptile |
|
Cloudflare preview deployed.
|
* origin/main: Install shared agent workflow seam (#143)
|
Codex closeout evidence for current head
Final state with merge_authority=ask: ready-no-merge-authority. |
What
A scheduled GitHub Actions bot that regenerates the committed prompt artifacts from react_on_rails
prompts.ymland opens a PR when they drift — mirroring react_on_rails' ownupdate-llms-full.yml.Why
The site
buildrunsprepare:prompts, which regeneratesprompts.ts/prompts.json/prompts/llms.txtfrom upstreamprompts.ymland fails on drift (scripts/prepare-prompts.mjs). Those files are committed, so whenever upstreamprompts.ymlchanges (e.g. shakacode/react_on_rails#4232) they go stale and every PR turns red until someone regenerates by hand — exactly what just happened on #136. This keeps them fresh automatically.How
schedule,workflow_dispatch, and thedocs-updatedrepository_dispatchreact_on_rails already sends to this repo.npm run prepareephemeral-clones react_on_railsmain(viaREACT_ON_RAILS_REPO_URL/REF, same as the build job) and regenerates.add-paths); the change-detection is also scoped to those 3 files.Notes for the maintainer
GITHUB_TOKENdon't auto-trigger thebuildcheck; review the small generated diff and merge (or enable auto-merge). I can add a check-dispatch step if you'd prefer it fully hands-off.🤖 Generated with Claude Code