Skip to content

Docs landing page + CI quality gate + release workflow - #2

Merged
bmadcode merged 1 commit into
mainfrom
release-1.0
Jul 8, 2026
Merged

Docs landing page + CI quality gate + release workflow#2
bmadcode merged 1 commit into
mainfrom
release-1.0

Conversation

@bmadcode

@bmadcode bmadcode commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #1:

  • docs/index.html so GitHub Pages (serve main /docs) has a landing page for the two slide guides
  • quality.yaml: runs every skill test suite and the genericity release gate on PRs; this PR is its first live run
  • release.yaml: push-button releases (marketplace.json version bump, tag, cosign keyless signature, GitHub Release from the CHANGELOG section)

- docs/index.html: film-themed landing page for GitHub Pages linking both
  slide guides and the user guide
- .github/workflows/quality.yaml: every skill test suite plus the
  genericity release gate on all PRs (ffmpeg and chromium installed so the
  render and HTML-graphics suites exercise instead of skip)
- .github/workflows/release.yaml: manual dispatch bumps the version in
  marketplace.json, commits, tags, keyless-signs the tag with cosign, and
  creates the GitHub Release with the matching CHANGELOG section
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 52 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: 789c89ed-12d4-4d3d-aa04-f290ea2f822d

📥 Commits

Reviewing files that changed from the base of the PR and between 9a54a41 and 51797b8.

📒 Files selected for processing (3)
  • .github/workflows/quality.yaml
  • .github/workflows/release.yaml
  • docs/index.html
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-1.0

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.

@bmadcode
bmadcode merged commit 728dfbd into main Jul 8, 2026
2 checks passed
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.

1 participant