Skip to content

print the plugin list from the registry, commit none - #208

Open
adssib wants to merge 2 commits into
pl-r2-providersfrom
pl-r3-nolists
Open

adssib wants to merge 2 commits into
pl-r2-providersfrom
pl-r3-nolists

Conversation

@adssib

@adssib adssib commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Stacked on #184. Refs #173 (I19.2), part of #171.

What this changes

No hand-kept list of plugins anywhere in this repo.

  • Deleted: docs/plugins.md, docs/plugins.json, the README's coverage table and plugin-count badge, the page table in providers/README.md.
  • cmd/list-plugins prints the list from the registry at run time, as JSON (make plugins): every provider (id, name, category, homepage) with its sources (id provider/source, old slug as alias, kind, layer, what it watches, URLs, page). -ref <tag> links the pages at a release. docs/plugins.schema.json describes the new shape; a test validates the output against it and checks its enums against plugin.Categories(), plugin.Layers() and the kinds on disk.
  • Release workflow: one step after the tag step runs go run ./cmd/list-plugins -ref "$TAG" and gh release create attaches the output as the release asset plugins.json (never committed). Consumers read https://github.com/patch-it-dev/patch-it-plugins/releases/latest/download/plugins.json, no token.
  • AGENTS.md rule 1 is now "every new or changed provider or source has complete metadata in its registration (and a providers/ page)"; CONTRIBUTING, the PR template, writing-a-plugin.md, docs/README.md, the README template (no count badges) and both review prompts say the same. There's no list to update.
  • cmd/new-plugin no longer writes a table row or regenerates a JSON file; --layer takes the registry's layers (api, sdk, …).

Checklist

  • Metadata complete in the registration: no source changes; every registration already passes RegisterProvider's checks
  • Every commit is signed off (DCO)
  • Golden tests: every golden byte-identical (36 files, sha256 compared with main)
  • testdata/README.md, drop tests, provider pages: not applicable
  • Fetches only through env.Get / core/kit/
  • make check passes locally
  • Nothing private

Notes for the reviewer

  • Until the first release with this change, releases/latest has no plugins.json: the docs site's build (build the plugin list from the plugins release asset patch-it-docs#12) then shows "the list is temporarily unavailable" rather than a stale copy. Releasing once after merging the stack fills it.
  • Nothing in the hosted ingestion service read docs/plugins.md or docs/plugins.json (checked: it imports the registry), so this changes nothing for it.

Calls I made (please check)

  • docs/plugins.schema.json stays committed: it's the shape of the asset, not a list, and the asset's $schema links it at the release's tag.
  • The release asset is generated in the step right after the tag is pushed (as asked) rather than before tagging; it can't realistically fail there since go test (which builds the same list) passed on that commit a few steps earlier.

Related PRs

🤖 Generated with Claude Code

docs/plugins.md and docs/plugins.json are gone, with the README's coverage
table and plugin-count badge and the providers/ page table. The registry is
the only list: go run ./cmd/list-plugins (make plugins) prints every provider
and source with its metadata as JSON (docs/plugins.schema.json), and the
Release workflow attaches that output to each release as plugins.json.

AGENTS.md rule 1 is now: every new or changed provider or source has complete
metadata in its registration, and a providers/ page. new-plugin no longer
writes a table row; the PR template and the review prompts check the
registration instead.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: adssib <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant