@theholocron/cli 5.0.0-alpha.215 → 5.0.0-alpha.217
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 +1 -1
- package/dist/cli.mjs +2 -2
- package/dist/cli.mjs.map +1 -1
- package/dist/plugin/capabilities.d.mts +1 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -548,7 +548,7 @@ commands and the config are provider-neutral; Discord is the first provider.
|
|
|
548
548
|
| `holocron notifications sync-roles` | Makes who holds a role match a GitHub team, through the links file (`--keep` only adds; `--provider` picks one) |
|
|
549
549
|
| `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 |
|
|
550
550
|
|
|
551
|
-
Channels fed by another service are declared with `feeds` on the channel: `{ name: "uptime", webhook: true, feeds: { monitoring: true } }` (the object form `{ name?, webhook?, avatar? }` overrides the alert channel's name, default `
|
|
551
|
+
Channels fed by another service are declared with `feeds` on the channel: `{ name: "uptime", webhook: true, feeds: { monitoring: true } }` (the object form `{ name?, webhook?, avatar? }` overrides the alert channel's name, default `Message to #<channel>`, the dedicated webhook's name, default the provider's, and gives that webhook a picture, a file path or `https://` URL, else the layout's `webhookAvatar`). `setup` gives the channel a dedicated webhook and hands its URL straight to the `monitoring` provider through `Monitoring.ensureAlertChannel({ name, format: "discord", url? })`, which finds an alert channel of that name or creates one and subscribes every check; the URL is never stored as a secret. It needs a `monitoring` provider that implements `ensureAlertChannel` (Checkly does). Two feeds may not share an alert channel name, and a feed's webhook may not share the channel's own webhook name (compared without regard to case).
|
|
552
552
|
|
|
553
553
|
Pinned messages are declared under the provider's `layout` as `pinned: [{ channel, content }]` (`channel` is a channel in the layout, `content` up to 2000 characters); the layout is the whole set of messages the bot has pinned in those channels.
|
|
554
554
|
|
package/dist/cli.mjs
CHANGED
|
@@ -4898,12 +4898,12 @@ function webhookAvatarOf(layout, webhook) {
|
|
|
4898
4898
|
function feedAvatarOf(layout, feed) {
|
|
4899
4899
|
return (typeof feed === "object" ? feed.avatar : void 0) ?? layout.webhookAvatar;
|
|
4900
4900
|
}
|
|
4901
|
-
/** The names a channel's monitoring feed uses: the alert channel (`
|
|
4901
|
+
/** The names a channel's monitoring feed uses: the alert channel (`Message to #uptime`) and its dedicated webhook (`Checkly`). */
|
|
4902
4902
|
function monitoringFeed(channel, feed, monitoring) {
|
|
4903
4903
|
const own = typeof feed === "object" ? feed : {};
|
|
4904
4904
|
const provider = monitoring.providerName;
|
|
4905
4905
|
return {
|
|
4906
|
-
name: own.name ?? `
|
|
4906
|
+
name: own.name ?? `Message to #${channel}`,
|
|
4907
4907
|
webhook: own.webhook ?? provider.charAt(0).toUpperCase() + provider.slice(1)
|
|
4908
4908
|
};
|
|
4909
4909
|
}
|