Fix main branch CI failures after MkDocs migration. - #183
Conversation
maryamtahhan
commented
Jul 30, 2026
- Remove stale mkdocs.yml nav entry for docs/blog/rhaiis-hello-world.md (file was deleted in prior commit; strict MkDocs build was aborting)
- Add .nojekyll to prevent GitHub's legacy Jekyll builder from running (Ansible YAML files were crashing Jekyll with Liquid syntax errors)
- Add explicit CodeQL workflow scanning Python and Actions only (default auto-scan was failing on Ruby after Gemfile removal)
- Remove stale mkdocs.yml nav entry for docs/blog/rhaiis-hello-world.md (file was deleted in prior commit; strict MkDocs build was aborting) - Add .nojekyll to prevent GitHub's legacy Jekyll builder from running (Ansible YAML files were crashing Jekyll with Liquid syntax errors) - Add explicit CodeQL workflow scanning Python and Actions only (default auto-scan was failing on Ruby after Gemfile removal) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
|
Warning Review limit reached
Next review available in: 5 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 (7)
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 |
Add symlink-aware edit links, ship .nojekyll in the Pages artifact, align homepage URLs, and refresh preview deps when requirements change. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
The repo has GitHub's Default Setup for CodeQL already enabled, so the custom codeql.yml workflow causes uploads to fail with "CodeQL analyses from advanced configurations cannot be processed when the default setup is enabled". Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>