Skip to content

Follow-up: remove legacy _tools and unused minima dependency - #188

Merged
lordfolken merged 1 commit into
masterfrom
chore/reduce-build-complexity
Jul 7, 2026
Merged

Follow-up: remove legacy _tools and unused minima dependency#188
lordfolken merged 1 commit into
masterfrom
chore/reduce-build-complexity

Conversation

@lordfolken

Copy link
Copy Markdown
Member

Summary

  • remove legacy _tools/ scripts/templates that are no longer referenced by build/deploy flows
  • remove unused minima gem from Gemfile
  • refresh Gemfile.lock and update internal structure docs accordingly

Test plan

  • docker run --rm --network host -v \"$PWD:/data\" -w /data ruby:4 bash -lc \"bundle install\"
  • docker run --rm --network host -v \"$PWD:/data\" -w /data ruby:4 bash -lc \"bundle install && bundle exec jekyll build --future\"

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 45 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 30f11f2f-8869-438f-b778-41b6e50fee57

📥 Commits

Reviewing files that changed from the base of the PR and between cf521b6 and 3ea4a27.

⛔ Files ignored due to path filters (1)
  • Gemfile.lock is excluded by !**/*.lock
📒 Files selected for processing (9)
  • Gemfile
  • _tools/fabfile.py
  • _tools/ftp_index/create_ftp_index.py
  • _tools/ftp_index/create_local_index.py
  • _tools/ftp_index/file.tpl
  • _tools/ftp_index/index.tpl
  • _tools/ftp_index/readme.tpl
  • _tools/ftp_index/subdir.tpl
  • docs/internal/WEBSITE_STRUCTURE.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/reduce-build-complexity

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.

Delete unreferenced _tools helpers and templates, drop the unused minima gem, and refresh Gemfile.lock to match the reduced dependency set.
@lordfolken
lordfolken force-pushed the chore/reduce-build-complexity branch from 0bfdad2 to 3ea4a27 Compare July 7, 2026 22:05
@lordfolken
lordfolken merged commit c42bc98 into master Jul 7, 2026
3 checks passed
@lordfolken
lordfolken deleted the chore/reduce-build-complexity branch July 7, 2026 22:06
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