ci: run docs health check on pushes to master - #677
Conversation
The workflow only ran on pull requests and on the weekly schedule, so nothing verified master after a merge. Two pull requests can each be green on their own and still break once combined, which is easy to hit with dependency updates that land close together. Adding the push trigger builds master right after every merge, so a broken combination is caught within minutes instead of at the next weekly run. Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mesutoezdil The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for project-hami ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 27 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)
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 |
1 participant
Add a
pushtrigger onmasterto the Docs Health Check workflow.The workflow currently runs only on pull requests and on the weekly Monday cron, so nothing builds
masterafter a merge.Two pull requests can each pass on their own and still break once combined, because each one is tested against the base as it was when the branch was created, not against the tree it actually lands on. Dependency updates that land close together are the common case: this repo merged four of them today.
Right now that breakage would sit on
masteruntil the next Monday run, or until someone opened an unrelated pull request and noticed.With the push trigger,
masteris linted, formatted, built and link-checked within minutes of every merge.