docs: explain managed ignore reconciliation#46
Conversation
✅ Deploy Preview for arashi-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…econciliation # Conflicts: # docs/commands/create.md # docs/workflows/index.md
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1ea4dbb2ef
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - `--repos-dir <path>` set a custom repos directory (default `./repos`). | ||
| - `--worktrees-dir <path>` set a custom worktree base directory (default `.arashi/worktrees`). | ||
| - `--ignore-scope <local|tracked|none>` choose repository-local rules, tracked rules, or no ignore-file writes. |
There was a problem hiding this comment.
Gate managed-ignore docs on shipped CLI support
The current published Arashi CLI contract for v1.19.2 lists init options as --dry-run, --force, --json, --no-discover, --repos-dir, --verbose, and --worktrees-dir, with no --ignore-scope; issue #213 is still an open proposal. If this docs site is published before the CLI implementation lands, users copying the new arashi init --ignore-scope ... examples will get an unknown-option failure, and the documented default .git/info/exclude behavior will be false. Please either version/feature-gate this content or wait until the CLI support ships.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
This would be updated along with the cli, a short window where the doc is out of date is ok for this project.
Summary
Validation
pnpm validategit diff --checkRelated PRs
Tracks corwinm/arashi-arashi#213.