@feigi/fleet-ctl 3.88.10 → 3.88.12
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.
package/package.json
CHANGED
|
@@ -138,7 +138,13 @@ cause. No fix command is recorded; the Check step only reports. A hook that
|
|
|
138
138
|
rewrites a file the PR does not otherwise change is the same stale base. Stage
|
|
139
139
|
every change of your own before the commit that runs the hook, so every change
|
|
140
140
|
still unstaged after it is the hook's alone: never stage those, `git restore --
|
|
141
|
-
<that path>` for each such path alone, then rebase and re-run.
|
|
141
|
+
<that path>` for each such path alone, then rebase and re-run. An untracked path
|
|
142
|
+
no ignore rule covers, still present after that commit, is the hook's alone too,
|
|
143
|
+
since your own new files were staged with the rest: never stage it, `git clean
|
|
144
|
+
-fd -- <that path>` for each such path alone, a directory as `recipe-check.mjs`
|
|
145
|
+
lists it (`dir/`), then rebase and re-run. That command never deletes an
|
|
146
|
+
ignored file. A path the re-run still refuses after that clean → bail with that
|
|
147
|
+
cause.
|
|
142
148
|
|
|
143
149
|
**In a detached worktree, push by refspec.** `run-team`'s runbook re-creates an
|
|
144
150
|
already-open PR's worktree with `git worktree add --detach <path> origin/<branch>`,
|
|
@@ -88,7 +88,12 @@ step only reports. A hook that rewrites a file the PR does not otherwise change
|
|
|
88
88
|
is the same stale base. Stage every change of your own before the commit that
|
|
89
89
|
runs the hook, so every change still unstaged after it is the hook's alone:
|
|
90
90
|
never stage those, `git restore -- <that path>` for each such path alone, then
|
|
91
|
-
rebase and re-run.
|
|
91
|
+
rebase and re-run. An untracked path no ignore rule covers, still present after
|
|
92
|
+
that commit, is the hook's alone too, since your own new files were staged with
|
|
93
|
+
the rest: never stage it, `git clean -fd -- <that path>` for each such path
|
|
94
|
+
alone, a directory as `recipe-check.mjs` lists it (`dir/`), then rebase and
|
|
95
|
+
re-run. That command never deletes an ignored file. A path the re-run still
|
|
96
|
+
refuses after that clean → push nothing and report that cause.
|
|
92
97
|
|
|
93
98
|
**`recipe-check.mjs` is how you run `<checkCmd>` and `<testCmd>`:**
|
|
94
99
|
`~/.fleet/bin/fleet-run recipe-check.mjs --member <your name> --testCmd "<testCmd>" --reports <scratch>/reports`,
|