ci: publish docs artifact for the portal mirror - #27
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 39 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)
Comment |
docs.byteveda.org/<slug>/404s today. GitHub Pages binds a custom domain to exactlyone repository, so this repo cannot serve a subpath of a domain held by
ByteVeda/byteveda.site— setting the domain here just reports already taken byanother repository.
Instead the docs portal mirrors each tool's build into its own export
(ByteVeda/byteveda.site#220).
This repo's own
byteveda.github.io/<slug>/site is unaffected — the docs are copied,not moved.
The portal cannot use the existing
github-pagesartifact:upload-pages-artifacthardcodes a 1-day retention, so it has always expired by the time the portal next
builds (all five tool repos currently report
expired: true). This adds one steppublishing the same directory as
docs-distwith a 90-day retention.No change to how this repo builds or deploys its docs.