From 70bf6cdbc811f074fcbce1a61b905054203e9020 Mon Sep 17 00:00:00 2001 From: Alex Clarke Date: Mon, 24 Aug 2026 10:03:51 -0600 Subject: [PATCH] Point at the renamed coyote-bundle-template starter repo --- REPL.md | 2 +- Sharing-Configurations.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/REPL.md b/REPL.md index 7a6de33..b0f1c60 100644 --- a/REPL.md +++ b/REPL.md @@ -450,7 +450,7 @@ The CLI equivalent is `coyote --install ` (with `--git-host`, `- accepting the same values). Use `.list bundles` to see what's installed and `.uninstall ` to remove a bundle. See [Sharing Configurations](Sharing-Configurations) for the expected repo layout, conflict resolution, secret handling, -and the [coyote-config-template](https://github.com/Dark-Alex-17/coyote-config-template) starter you can fork. +and the [coyote-bundle-template](https://github.com/Dark-Alex-17/coyote-bundle-template) starter you can fork. ## `.uninstall` - Uninstall a bundle diff --git a/Sharing-Configurations.md b/Sharing-Configurations.md index feb3851..f27fa2d 100644 --- a/Sharing-Configurations.md +++ b/Sharing-Configurations.md @@ -21,7 +21,7 @@ This page covers the expected repository layout, bundle identity, provenance tra handling, and how to publish your own bundle. To see a template repository with all recognized categories, see the -[coyote-config-template](https://github.com/Dark-Alex-17/coyote-config-template) repository. +[coyote-bundle-template](https://github.com/Dark-Alex-17/coyote-bundle-template) repository. --- @@ -451,7 +451,7 @@ To share your Coyote configuration, structure a git repo like the layout above a self-hosted Forgejo instance, etc. The easiest way to start is to **fork the official template repo**: -[`coyote-config-template`](https://github.com/Dark-Alex-17/coyote-config-template). It includes a working sample of each +[`coyote-bundle-template`](https://github.com/Dark-Alex-17/coyote-bundle-template). It includes a working sample of each asset type plus a `README` describing the customization workflow. ### Best practices