Repository navigation
docs(guide): lift the getting-started, install, and setup guides - #941
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 53 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 Run ID: 📒 Files selected for processing (3)
Comment |
The installer puts `min` on PATH (per the README), so the post-install sanity check should use the session CLI's `min --version`, not `mip`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the mip-centric init/update walkthrough with the session-first flow: `min init` scaffolds minimal.toml (including the `[session]` block it really generates), declare the session's tools in that block, then `min activate --attach .` to create and enter an isolated session. Uses `min` throughout, per the session-first product framing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
| Edit the `packages` list under `[session]` to add whatever your team works with. Extend the existing list; do not add a second `[session]` table, since TOML does not allow a table to be defined twice. | ||
|
|
||
| ```toml | ||
| [session] # min attach |
There was a problem hiding this comment.
should the comment be min activate instead? I see this in the init toml file also
There was a problem hiding this comment.
TBH; at a glance this comment doesn't seem very helpful
Quote the getting-started frontmatter description, require unprivileged user namespaces with a linux-host-setup link, align the macOS floor with the README (Apple Silicon, M1 or later), describe activation as seeding the sandbox with a project copy, note the min init confirmation prompt and the pip/uv stack names, explain [defaults], and add Upgrade and Uninstall sections per review. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Lift the Start pages (getting-started, install, setup) into docs/guide/, de-numbered and GitHub-first: em-dashes removed, harness renamed to stack ([stack] TOML block, verified against mfile), package/build commands mapped to mip (init/update/--version), and the install guide uses the stable channel (https://go.minimal.dev/stable) in every install command. No profiles content, no private repo names. Cross-links resolve once #863 and sibling docs-lift PRs merge; verification greps (em-dash, harness/profile/unstable, root-relative doc links) all clean.
Note
Add getting-started, install, and setup guides to the Minimal docs
Adds three new documentation pages to the guide section covering the full onboarding flow for Minimal.
min init, theminimal.tomlconfig structure, and how to enter a session withmin activate --attach ..Changes since #941 opened
Macroscope summarized 82ef622.