Skip to content

ci: publish docs artifact for the portal mirror - #27

Merged
kartikeya-27 merged 1 commit into
masterfrom
ci/docs-portal-mirror
Aug 5, 2026
Merged

kartikeya-27 merged 1 commit into
masterfrom
ci/docs-portal-mirror

Conversation

@pratyush618

Copy link
Copy Markdown
Collaborator

docs.byteveda.org/<slug>/ 404s today. GitHub Pages binds a custom domain to exactly
one repository, so this repo cannot serve a subpath of a domain held by
ByteVeda/byteveda.site — setting the domain here just reports already taken by
another 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-pages artifact: upload-pages-artifact
hardcodes 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 step
publishing the same directory as docs-dist with a 90-day retention.

No change to how this repo builds or deploys its docs.

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e0bceb48-955d-4c9f-a55c-443ecc1911f2

📥 Commits

Reviewing files that changed from the base of the PR and between 42441b0 and 40fcf38.

📒 Files selected for processing (1)
  • .github/workflows/docs.yml

Comment @coderabbitai help to get the list of available commands.

@kartikeya-27
kartikeya-27 merged commit 897886a into master Aug 5, 2026
8 checks passed
@kartikeya-27
kartikeya-27 deleted the ci/docs-portal-mirror branch August 5, 2026 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants