Wire tmux-tell + cellblock into reusable-changelog-fragment-check.yml (post-v0.20.0-cut) #280

New issue

Closed

opened 2026-07-02 10:11:54 +02:00 by quartermaster · 0 comments

quartermaster commented

2026-07-02 10:11:54 +02:00

Owner

Why

Split from release-toolkit#271 (fragment-kind PR-gate reusable, landed in PR #278). AC #3 of the original issue named this as follow-up work:

tmux-tell wires the new check in once landed; future .documentation.md-style mistakes fail PR check before merge

Filed as a discrete tracker per Surveyor's non-blocking note on the #278 review (2026-07-02):

file the AC#3 follow-up tracker now (not prose)

What

Once v0.20.0-stable cuts with the new reusable-changelog-fragment-check.yml, wire the check into the two consumer repos that most benefit from it:

tmux-tell — the empirical anchor (.documentation.md → tmux-tell#655 → #658 recovery on 2026-06-30 is what motivated the whole feature). Add .forgejo/workflows/fragment-check.yml pinned to @v0.20.0 (or the current released tag by then), matching the wiring stanza in docs/integration.md § fragment-check.yml.
cellblock — sibling consumer using release-toolkit already; same wiring stanza + version pin.

Both changes are single-file additions in the consumer repos. Each PR should reference this tracker + the parent #271.

Acceptance criteria

tmux-tell has .forgejo/workflows/fragment-check.yml pinned to the current released release-toolkit tag, on main.
cellblock has the same file on main.
Empirical verification: a PR against either repo that adds an unknown-kind fragment (e.g. .documentation.md) fails the new check before merge.

Refs

Parent: release-toolkit#271
Fix substrate: release-toolkit#278 (PR)
Empirical anchor: tmux-tell#655 (unknown-kind fragment) → tmux-tell#658 (rename recovery), 2026-06-30
Docs: release-toolkit integration.md § fragment-check.yml

Blocked-on

release-toolkit v0.20.0-stable cut (held pending PR #278 landing per Bosun 2026-07-02).

## Why Split from release-toolkit#271 (fragment-kind PR-gate reusable, landed in PR #278). AC #3 of the original issue named this as follow-up work: > 3. tmux-tell wires the new check in once landed; future `.documentation.md`-style mistakes fail PR check before merge Filed as a discrete tracker per Surveyor's non-blocking note on the #278 review (2026-07-02): > file the AC#3 follow-up tracker now (not prose) ## What Once `v0.20.0-stable` cuts with the new `reusable-changelog-fragment-check.yml`, wire the check into the two consumer repos that most benefit from it: - **tmux-tell** — the empirical anchor (`.documentation.md` → tmux-tell#655 → #658 recovery on 2026-06-30 is what motivated the whole feature). Add `.forgejo/workflows/fragment-check.yml` pinned to `@v0.20.0` (or the current released tag by then), matching the wiring stanza in [docs/integration.md § fragment-check.yml](https://git.frankenbit.de/frankenbit/release-toolkit/src/branch/main/docs/integration.md). - **cellblock** — sibling consumer using release-toolkit already; same wiring stanza + version pin. Both changes are single-file additions in the consumer repos. Each PR should reference this tracker + the parent #271. ## Acceptance criteria 1. tmux-tell has `.forgejo/workflows/fragment-check.yml` pinned to the current released release-toolkit tag, on main. 2. cellblock has the same file on main. 3. Empirical verification: a PR against either repo that adds an unknown-kind fragment (e.g. `.documentation.md`) fails the new check before merge. ## Refs - Parent: release-toolkit#271 - Fix substrate: release-toolkit#278 (PR) - Empirical anchor: tmux-tell#655 (unknown-kind fragment) → tmux-tell#658 (rename recovery), 2026-06-30 - Docs: [release-toolkit integration.md § fragment-check.yml](https://git.frankenbit.de/frankenbit/release-toolkit/src/branch/main/docs/integration.md) ## Blocked-on release-toolkit `v0.20.0-stable` cut (held pending PR #278 landing per Bosun 2026-07-02).