arashi 1.19.1 → 1.20.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +22 -1
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -112,6 +112,7 @@ pnpm run build
112
112
  Arashi currently provides these commands:
113
113
 
114
114
  - `arashi init`
115
+ - [`arashi init --zero-config`](docs/standalone.md) for a single repository with `.worktrees/<branch>` paths and no persisted Arashi configuration
115
116
  - `arashi install`
116
117
  - `arashi update [--check] [--dry-run] [--yes]`
117
118
  - `arashi add <git-url>`
@@ -132,7 +133,8 @@ Arashi currently provides these commands:
132
133
  ## Quick Example
133
134
 
134
135
  ```bash
135
- arashi init
136
+ arashi init # repository-local ignore rules (default)
137
+ arashi init --ignore-scope tracked # opt in to a shared .gitignore block
136
138
  arashi add git@github.com:your-org/frontend.git
137
139
  arashi add git@github.com:your-org/backend.git
138
140
  arashi create feature-auth-refresh
@@ -148,6 +150,25 @@ arashi switch --cd feature-auth-refresh # parent-shell cd when shell integra
148
150
  arashi switch --no-default-launch # bypass configured launch mode defaults once
149
151
  ```
150
152
 
153
+ ### Managed Git ignore rules
154
+
155
+ Configured workspaces keep `reposDir` and `worktreesDir` effectively ignored. Arashi asks Git
156
+ first, so an existing tracked `.gitignore`, repository-local `.git/info/exclude`, or configured
157
+ global excludes rule is honored without duplication. Missing safe repository-relative rules use
158
+ the common repository's local exclude file by default, including when a command runs in a linked
159
+ worktree.
160
+
161
+ Use `arashi init --ignore-scope tracked` when the team wants Arashi-owned rules committed in the
162
+ workspace `.gitignore`. Use `arashi init --ignore-scope none` for a fully manual workflow; Arashi
163
+ will warn about unignored managed paths but will not edit ignore files. Running
164
+ `arashi init --ignore-scope local` resets that clone-local preference without recreating an
165
+ existing workspace. The explicit `tracked` or `none` preference is stored only in local Git config
166
+ as `arashi.ignoreScope`; Arashi never creates or modifies global Git ignore configuration.
167
+
168
+ `init`, `pull`, `clone`, `add`, and `create` reconcile the same owned rules before materializing
169
+ configured repositories or worktrees. `doctor` reports missing, unsafe, invalid, or stale managed
170
+ ignore state without changing it.
171
+
151
172
  ## Workflow Guides
152
173
 
153
174
  Use the docs site workflow guides when you want setup guidance by outcome instead of by individual command.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "arashi",
3
- "version": "1.19.1",
3
+ "version": "1.20.0",
4
4
  "description": "Git worktree manager for meta-repositories - The eye of the storm for your development workflow",
5
5
  "keywords": [
6
6
  "cli",
@@ -81,7 +81,7 @@
81
81
  "commander": "12.1.0",
82
82
  "conventional-changelog-conventionalcommits": "8.0.0",
83
83
  "husky": "9.1.7",
84
- "js-yaml": "4.1.1",
84
+ "js-yaml": "4.2.0",
85
85
  "lint-staged": "16.2.7",
86
86
  "ora": "8.2.0",
87
87
  "oxfmt": "0.28.0",
@@ -89,7 +89,7 @@
89
89
  "semantic-release": "25.0.6",
90
90
  "ts-json-schema-generator": "2.4.0",
91
91
  "typescript": "5.9.3",
92
- "vitest": "3.2.4"
92
+ "vitest": "4.1.10"
93
93
  },
94
94
  "lint-staged": {
95
95
  "*.{ts,tsx,js,mjs,cjs,json,md,yml,yaml}": "oxfmt --config .oxfmtrc.json --write"