Skip to content

Fix osac-ux GitHub Pages source branch - #141

Open
liatb-rh wants to merge 1 commit into
osac-project:mainfrom
liatb-rh:fix/osac-ux-pages-branch
Open

Fix osac-ux GitHub Pages source branch#141
liatb-rh wants to merge 1 commit into
osac-project:mainfrom
liatb-rh:fix/osac-ux-pages-branch

Conversation

@liatb-rh

Copy link
Copy Markdown
Contributor

Pages for osac-ux was configured to build from the 0.1 source branch, which is a plain code snapshot rendered via Jekyll (this is why https://osac-project.github.io/osac-ux/ shows the placeholder public_template README instead of the app).

The actual demo app is built and published by the deploy-pages.yml workflow to the gh-pages branch. This points Pages at gh-pages instead so it serves the built app.

Pages was configured to build from the "0.1" source branch, which is
a plain code snapshot rendered via Jekyll (showing the placeholder
public_template README). The actual demo app is built and published
by the deploy-pages.yml workflow to the gh-pages branch. Point Pages
at gh-pages so it serves the built app instead.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@liatb-rh, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 22 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: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3d3e4308-1566-491f-aff1-42d42efdc2f1

📥 Commits

Reviewing files that changed from the base of the PR and between 6effc13 and 548d58a.

📒 Files selected for processing (1)
  • repositories.tf
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

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

@larsks

larsks commented Jul 27, 2026

Copy link
Copy Markdown
Member

@liatb-rh this needs to be rebased. Thanks!

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