hushrun 0.11.1 → 0.12.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/package.json +7 -7
  2. package/skills/hushrun/SKILL.md +20 -11
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hushrun",
3
- "version": "0.11.1",
3
+ "version": "0.12.0",
4
4
  "description": "Skip tests, lint and typecheck when this exact code already passed them, on laptops, in CI and in coding agents' sandboxes.",
5
5
  "keywords": [
6
6
  "ci",
@@ -45,11 +45,11 @@
45
45
  "node": ">=18"
46
46
  },
47
47
  "optionalDependencies": {
48
- "@hushrun/cli-darwin-arm64": "0.11.1",
49
- "@hushrun/cli-darwin-x64": "0.11.1",
50
- "@hushrun/cli-linux-arm64": "0.11.1",
51
- "@hushrun/cli-linux-x64": "0.11.1",
52
- "@hushrun/cli-win32-arm64": "0.11.1",
53
- "@hushrun/cli-win32-x64": "0.11.1"
48
+ "@hushrun/cli-darwin-arm64": "0.12.0",
49
+ "@hushrun/cli-darwin-x64": "0.12.0",
50
+ "@hushrun/cli-linux-arm64": "0.12.0",
51
+ "@hushrun/cli-linux-x64": "0.12.0",
52
+ "@hushrun/cli-win32-arm64": "0.12.0",
53
+ "@hushrun/cli-win32-x64": "0.12.0"
54
54
  }
55
55
  }
package/skills/hushrun/SKILL.md CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  name: hushrun
3
- description: Use before every git push in a repository that uses hushrun, when hushrun's pre-push hook refuses a push, when a line starts with "hushrun:", and when asked to set hushrun up. hushrun skips CI checks that this exact code already passed, so running them here first means CI doesn't run them again.
3
+ description: Use before every git push in a repository that uses hushrun, when hushrun's pre-push hook refuses a push, when a line starts with "hushrun:", and when asked to set hushrun up. hushrun skips a check that this exact code already passed, here and, once the repository shares its results, in CI, so running checks here first means CI doesn't run them again.
4
4
  compatibility: hushrun 0.11.0 or newer for `hushrun guide`; everything else here works with any hushrun.
5
5
  metadata:
6
- hushrun-skill: "1"
6
+ hushrun-skill: "2"
7
7
  ---
8
8
 
9
9
  # hushrun
10
10
 
11
- hushrun remembers which checks passed on which files. A pass here skips the same check in CI, on
12
- any branch or commit with the same files.
11
+ hushrun remembers which checks passed on which files. A pass here skips the same check here, on
12
+ any branch or commit with the same files, and in CI too once the repository shares its results.
13
13
 
14
14
  This skill holds what every hushrun does the same way. **Run `hushrun guide` once per session.**
15
15
  It prints the rest for the hushrun installed here, such as what each of its lines means, and says
@@ -22,14 +22,14 @@ In these commands, `hushrun` is `npx hushrun` where hushrun is a dev dependency
22
22
  ## Is hushrun here?
23
23
 
24
24
  A repository uses hushrun when its `package.json` has scripts that start with `hushrun run`, or a
25
- `"hushrun"` key that names a backend; in another language, when it has a `hushrun.yaml` that
26
- names a `backend`.
25
+ `"hushrun"` key that names a backend; in another language, when it has a `hushrun.yaml`, or its
26
+ CI's files run checks as `hushrun run …`.
27
27
 
28
28
  ## Before you push
29
29
 
30
30
  1. Commit your work.
31
- 2. Run `hushrun ready`. It lists what CI would still run on this exact code, and the commands that
32
- run it here, each in full, with the directory it runs in.
31
+ 2. Run `hushrun ready`. It lists the checks this exact code hasn't passed yet, which CI would
32
+ still run, and the commands that run them here, each in full, with the directory each runs in.
33
33
  3. Run those commands as printed, each on its own, so that each is the check CI looks for. If a
34
34
  check fails, fix the code, not the check.
35
35
  4. Run `hushrun ready` again until it says the code is ready, then push.
@@ -38,6 +38,14 @@ names a `backend`.
38
38
  exit code 10 means they are still to run. A check in state `ci` is one nothing here changes: CI or
39
39
  another machine runs it, and `why` says what it needs.
40
40
 
41
+ ## Where results stay on this machine
42
+
43
+ Results are shared only where hushrun has a backend and a sign-in or a token for it. Anywhere else
44
+ they stay on this machine: a check that passed here skips here, and CI runs every check.
45
+ `hushrun ready` says when that is so. The steps above are the same. Sharing is the person's to
46
+ decide: tell them what `hushrun ready` said, and don't sign in or run `hushrun init` for it unless
47
+ they ask.
48
+
41
49
  ## When a push is refused
42
50
 
43
51
  hushrun's pre-push hook refuses a coding agent's push while a check that can run here hasn't
@@ -61,14 +69,15 @@ is the repository's, the binary is theirs, and an update changes the tool you ar
61
69
  ## Reporting back
62
70
 
63
71
  Say which checks hushrun skipped because this code passed them before, which `hushrun ready` left
64
- to CI (`ci`), and anything hushrun said is out of date.
72
+ to CI (`ci`), whether it said results stay on this machine, and anything hushrun said is out of
73
+ date.
65
74
 
66
75
  ## Setting hushrun up
67
76
 
68
77
  When a person asks you to add hushrun to a repository, run `npx hushrun init --yes` at its root.
69
78
  It prints a sign-in link and a code: show both to the person and wait, since only they can approve
70
- it. Then show them the diff. `hushrun guide` covers the rest, such as a person in several
71
- organizations, and sandboxes with no browser.
79
+ it. Then show them the diff. `hushrun guide` covers the rest, such as setting up with no account,
80
+ a person in several organizations, and sandboxes with no browser.
72
81
 
73
82
  ## Never
74
83