@theholocron/cli 5.0.0-alpha.275 → 5.0.0-alpha.277
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/README.md +4 -3
- package/dist/cli.mjs +5315 -5117
- package/dist/cli.mjs.map +1 -1
- package/dist/{index-Cs7LmYWL.d.mts → index-D_HJGtOY.d.mts} +78 -2
- package/dist/{index-DgjlIpm1.d.mts → index-dMk1XHFO.d.mts} +1 -1
- package/dist/index.d.mts +3 -3
- package/dist/plugin/capabilities.d.mts +2 -2
- package/dist/presets.d.mts +1 -1
- package/package.json +12 -12
package/README.md
CHANGED
|
@@ -274,8 +274,9 @@ unverified/unattributed commit. Repository-admin bypass still covers the real
|
|
|
274
274
|
risk. And the `codecov.yml` `holocron repo setup` writes carries `if_not_found:
|
|
275
275
|
success` on every status default, so an infra-only PR (dep bump, config,
|
|
276
276
|
lockfile — no coverable change) passes instead of hanging on a `codecov/*`
|
|
277
|
-
required check that never posts.
|
|
278
|
-
an
|
|
277
|
+
required check that never posts. It also ignores `**/*.mdx`, so a docs-only PR that
|
|
278
|
+
adds pages is not judged to change testable files and left with an empty upload.
|
|
279
|
+
A re-run of `holocron repo setup` backfills all of these into an existing repo.
|
|
279
280
|
|
|
280
281
|
### Default branch (`repo.defaultBranch`)
|
|
281
282
|
|
|
@@ -547,7 +548,7 @@ commands and the config are provider-neutral; Discord is the first provider.
|
|
|
547
548
|
| `holocron notifications create-server --name <n> --owner <id>` | Creates the server the layout describes, writes its id into the config, applies the layout, invites the owner, waits for them to join and hands the server over (`--resume` finishes an interrupted hand-over; `--force` allows a second server) |
|
|
548
549
|
| `holocron notifications link` | Links your account on the provider to your GitHub account by signing in with the provider (OAuth, nothing secret kept) |
|
|
549
550
|
| `holocron notifications sync-roles` | Makes who holds a role match a GitHub team, through the links file (`--keep` only adds; `--provider` picks one) |
|
|
550
|
-
| `holocron doctor notifications [--built-only] [--deliver]` | Step by step: does the server match the layout, do the secrets exist, and does a person (not the bot) own it. A full run also leaves one `🧪 test:` post in the layout's `testChannel`; `--built-only` posts nothing; `--deliver` posts to every channel and removes each post
|
|
551
|
+
| `holocron doctor notifications [--built-only] [--deliver]` | Step by step: does the server match the layout, do the secrets exist, and does a person (not the bot) own it. A full run also leaves one `🧪 test:` post in the layout's `testChannel`; `--built-only` posts nothing; `--deliver` posts to every channel and removes each post. It also reads the Checkly feed (webhook, alert channel, subscriptions) and the Comlink relay (Worker, route, bindings, the tracker's integration and rule), posting nothing, so `--built-only` keeps those steps |
|
|
551
552
|
| `holocron doctor variables` | Do the Actions variables `repo.variables` declares exist, with those values (and, for the organization's, that visibility)? One row for the repository and one for the organization, each only when declared. Read-only. An undeclared variable counts only with `prune`; a scope that cannot be read (no provider, no org token) is a skip, not a failure |
|
|
552
553
|
| `holocron doctor environments` | Do the deployment environments exist? The ones `repo setup` creates (`staging`, `production`, when an `environments` provider is configured) plus every environment `repo.secrets.environments` names. One row. A missing one fails; an extra one is never a problem; no provider with some named is a skip |
|
|
553
554
|
| `holocron doctor repo` | Do the repository settings `repo setup` writes match the config? One row per group the config declares: description and homepage, default branch and merge settings, topics, custom properties, team access, branch protection; labels and security settings are always checked. Read-only. Reads through optional `Source` methods (`getRepoInfo`, `getProperties`, `listLabels`, `listTeamAccess`, `getRulesetDetail`, `getSecurity`); a group that cannot be read is a skip, not a failure |
|