From 281d8d54cc1e604261325f06bab2ea5cd21a4671 Mon Sep 17 00:00:00 2001 From: Bret Mogilefsky Date: Sat, 20 Jun 2026 15:07:04 -0700 Subject: [PATCH] Update GitHub repo references from feedback* to feedBack* --- README.md | 6 +++--- docs/github-setup.md | 2 +- docs/guidelines.md | 2 +- docs/pipeline.md | 6 +++--- docs/plugins.md | 10 +++++----- runbooks/hotfix.md | 6 +++--- runbooks/plugin-migration.md | 2 +- runbooks/release.md | 6 +++--- scripts/apply-ruleset-core-checks.sh | 2 +- scripts/apply-ruleset-core.sh | 2 +- scripts/apply-ruleset-plugins.sh | 2 +- 11 files changed, 23 insertions(+), 23 deletions(-) diff --git a/README.md b/README.md index f9cf77d..a5c6667 100644 --- a/README.md +++ b/README.md @@ -29,6 +29,6 @@ Slopsmith uses a **release-centric branching model**. Each version gets its own | Repo | Role | |---|---| -| `got-feedback/feedback` | Core — FastAPI server, plugin loader, Docker image | -| `got-feedback/feedback-desktop` | Desktop — Electron wrapper, native audio engine | -| `got-feedback/feedback-plugin-*` | Org plugins — bundled in desktop, lighter governance | +| `got-feedback/feedBack` | Core — FastAPI server, plugin loader, Docker image | +| `got-feedback/feedBack-desktop` | Desktop — Electron wrapper, native audio engine | +| `got-feedback/feedBack-plugin-*` | Org plugins — bundled in desktop, lighter governance | diff --git a/docs/github-setup.md b/docs/github-setup.md index 5b3695f..99216d7 100644 --- a/docs/github-setup.md +++ b/docs/github-setup.md @@ -54,7 +54,7 @@ Issue forms gate new issue submissions to a structured format. Disable blank iss ### config.yml — disable blank issues ```yaml -# .github/ISSUE_TEMPLATE/config.yml (in got-feedback/feedback and got-feedback/feedback-desktop) +# .github/ISSUE_TEMPLATE/config.yml (in got-feedback/feedBack and got-feedback/feedBack-desktop) blank_issues_enabled: false contact_links: - name: Plugin issues diff --git a/docs/guidelines.md b/docs/guidelines.md index 5589d27..87f5e81 100644 --- a/docs/guidelines.md +++ b/docs/guidelines.md @@ -1,6 +1,6 @@ # DevOps Guidelines -Guidelines for contributors to `got-feedback/feedback` and `got-feedback/feedback-desktop`. For plugin-specific rules see [plugins.md](plugins.md). +Guidelines for contributors to `got-feedback/feedBack` and `got-feedback/feedBack-desktop`. For plugin-specific rules see [plugins.md](plugins.md). --- diff --git a/docs/pipeline.md b/docs/pipeline.md index 60fab5f..4ca4386 100644 --- a/docs/pipeline.md +++ b/docs/pipeline.md @@ -99,15 +99,15 @@ Trigger: `workflow_dispatch` on `slopsmith-desktop` with inputs: ## Plugin-lock pinning -Org plugins (`got-feedback/feedback-plugin-*`) are cloned by the desktop build at build time. For release builds, they are pinned to specific commits recorded in `plugin-lock.json` on the active `release/*` branch. Nightlies always use tip. +Org plugins (`got-feedback/feedBack-plugin-*`) are cloned by the desktop build at build time. For release builds, they are pinned to specific commits recorded in `plugin-lock.json` on the active `release/*` branch. Nightlies always use tip. `plugin-lock.json` is created when the release branch is cut (see [runbooks/release.md](../runbooks/release.md)) and can be updated via PR on the release branch if a specific plugin fix needs to ship in the release. Format: ```json { - "got-feedback/feedback-plugin-notedetect": "abc1234", - "got-feedback/feedback-plugin-piano": "def5678", + "got-feedback/feedBack-plugin-notedetect": "abc1234", + "got-feedback/feedBack-plugin-piano": "def5678", "masc0t/slopsmith-plugin-find-more": "ghi9012" } ``` diff --git a/docs/plugins.md b/docs/plugins.md index 37bcbfd..85b926e 100644 --- a/docs/plugins.md +++ b/docs/plugins.md @@ -8,15 +8,15 @@ Slopsmith distinguishes three plugin tiers with different integration levels and | Tier | Location | Ships via | Versioned with core | |---|---|---|---| -| **Core plugins** (`bundled: true`) | `got-feedback/feedback/plugins/` | Docker image + desktop | Yes — tied to core release | -| **Org plugins** | `got-feedback/feedback-plugin-*` repos | Desktop only | No — independent cadence | +| **Core plugins** (`bundled: true`) | `got-feedback/feedBack/plugins/` | Docker image + desktop | Yes — tied to core release | +| **Org plugins** | `got-feedback/feedBack-plugin-*` repos | Desktop only | No — independent cadence | | **Community plugins** | Personal accounts | Desktop only | No — migration target | --- ## Core plugins -Core plugins have `"bundled": true` in their `plugin.json`. They live directly in the `got-feedback/feedback` repository under `plugins/` and are the source of truth for what ships in the Docker image. +Core plugins have `"bundled": true` in their `plugin.json`. They live directly in the `got-feedback/feedBack` repository under `plugins/` and are the source of truth for what ships in the Docker image. **Governance:** full core contribution workflow applies. - PR required, CI must pass, 1 approval required @@ -34,7 +34,7 @@ Core plugins have `"bundled": true` in their `plugin.json`. They live directly i ## Org plugins -Org plugins live in their own repos under the `slopsmith` GitHub org (`got-feedback/feedback-plugin-*`). The desktop build clones them at build time via `build-common.sh`. +Org plugins live in their own repos under the `slopsmith` GitHub org (`got-feedback/feedBack-plugin-*`). The desktop build clones them at build time via `build-common.sh`. **Governance:** lighter model. Plugin authors own their workflow. @@ -57,7 +57,7 @@ The full core contribution guidelines apply only when a plugin is integrated int **Reusable CI workflow:** the `plugin-lint` job is defined as a reusable workflow in this repo. Org plugin repos call it rather than maintaining their own lint logic: ```yaml -# .github/workflows/ci.yml in any got-feedback/feedback-plugin-* repo +# .github/workflows/ci.yml in any got-feedback/feedBack-plugin-* repo jobs: plugin-lint: uses: slopsmith/.github/.github/workflows/plugin-lint.yml@main diff --git a/runbooks/hotfix.md b/runbooks/hotfix.md index 15061aa..dc5a2c5 100644 --- a/runbooks/hotfix.md +++ b/runbooks/hotfix.md @@ -18,13 +18,13 @@ Step-by-step checklist for applying an urgent fix to an already-shipped version. ### 1 — Branch from the release branch ```bash -# In got-feedback/feedback +# In got-feedback/feedBack git fetch origin git checkout release/vX.Y.Z git checkout -b hotfix/-short-description ``` -Do the same in `got-feedback/feedback-desktop` if the fix touches desktop code. +Do the same in `got-feedback/feedBack-desktop` if the fix touches desktop code. ### 2 — Fix and PR @@ -51,7 +51,7 @@ Monitor `release.yml` — Docker image should appear on GHCR as `:vX.Y.Z+1`. ### 5 — Tag desktop ```bash -# In got-feedback/feedback-desktop, on release/vX.Y.Z +# In got-feedback/feedBack-desktop, on release/vX.Y.Z git tag vX.Y.Z+1 git push origin vX.Y.Z+1 ``` diff --git a/runbooks/plugin-migration.md b/runbooks/plugin-migration.md index 9028c57..43f13f2 100644 --- a/runbooks/plugin-migration.md +++ b/runbooks/plugin-migration.md @@ -72,7 +72,7 @@ Change the entry in `scripts/build-common.sh` from the personal account to the o /slopsmith-plugin- # After -got-feedback/feedback-plugin- +got-feedback/feedBack-plugin- ``` Open a PR on the active `release/*` branch of `slopsmith-desktop`. Also update `plugin-lock.json` to point to the new repo's HEAD commit. diff --git a/runbooks/release.md b/runbooks/release.md index 08c3905..d720e88 100644 --- a/runbooks/release.md +++ b/runbooks/release.md @@ -10,7 +10,7 @@ Step-by-step checklist for cutting a Slopsmith release. Follow in order — step Do this at the beginning of a development cycle, not just before shipping. -- [ ] Open a milestone tracking issue: **"vX.Y.Z milestone"** in `got-feedback/feedback` listing all planned features. Link relevant issues to it. +- [ ] Open a milestone tracking issue: **"vX.Y.Z milestone"** in `got-feedback/feedBack` listing all planned features. Link relevant issues to it. - [ ] Cut `release/vX.Y.Z` from `main` on **core**: ```bash git checkout main && git pull @@ -38,14 +38,14 @@ Repeat as needed throughout the development cycle. - [ ] Confirm CI is green on `release/vX.Y.Z` in both repos - [ ] Tag core: ```bash - # In got-feedback/feedback, on release/vX.Y.Z + # In got-feedback/feedBack, on release/vX.Y.Z git tag vX.Y.Z-alpha.1 # or -beta.1, etc. git push origin vX.Y.Z-alpha.1 ``` - [ ] Monitor `release.yml` on core — Docker image should appear on GHCR within ~5 minutes - [ ] Tag desktop with the same tag: ```bash - # In got-feedback/feedback-desktop, on release/vX.Y.Z + # In got-feedback/feedBack-desktop, on release/vX.Y.Z git tag vX.Y.Z-alpha.1 git push origin vX.Y.Z-alpha.1 ``` diff --git a/scripts/apply-ruleset-core-checks.sh b/scripts/apply-ruleset-core-checks.sh index 4f65cfe..d6f7686 100644 --- a/scripts/apply-ruleset-core-checks.sh +++ b/scripts/apply-ruleset-core-checks.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # apply-ruleset-core-checks.sh # -# Applies the core-only CI checks to got-feedback/feedback: +# Applies the core-only CI checks to got-feedback/feedBack: # ci / tailwind-fresh # ci / manifest-validation # diff --git a/scripts/apply-ruleset-core.sh b/scripts/apply-ruleset-core.sh index 163a222..44c2d12 100644 --- a/scripts/apply-ruleset-core.sh +++ b/scripts/apply-ruleset-core.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # apply-ruleset-core.sh # -# Applies branch protection to got-feedback/feedback and got-feedback/feedback-desktop. +# Applies branch protection to got-feedback/feedBack and got-feedback/feedBack-desktop. # # Two rulesets per repo: # branch-protection (always active) — no force push/delete, PR + 1 approval diff --git a/scripts/apply-ruleset-plugins.sh b/scripts/apply-ruleset-plugins.sh index f912879..0ae8ac4 100644 --- a/scripts/apply-ruleset-plugins.sh +++ b/scripts/apply-ruleset-plugins.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # apply-ruleset-plugins.sh # -# Applies branch protection to org plugin repos (got-feedback/feedback-plugin-*). +# Applies branch protection to org plugin repos (got-feedback/feedBack-plugin-*). # # Two rulesets per repo: # plugin-branch-protection (always active) — no force push/delete