Skip to content

About

How patch-it notices when something your code depends on changes: APIs, packages, SDKs, runtimes, CI, AI models. You get the fix, not the alert.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Patchy, the patch-it bot, holding up the lines it found

patch-it-plugins

How patch-it notices, on its own, that something your code depends on changed. Each provider (Stripe, OpenAI, GitHub…) has sources (a spec, a changelog, a shutdown notice, a feed); a plugin reads every version of a source and turns what changed into a change event, with the source linked and quoted.

CI Go Reference Go version License: Apache-2.0 Docs Discussions

Add a provider in 15 minutes

You need Go (the version in go.mod), make and Python 3.

  1. Scaffold it, on the kind that reads its source (which kind?); in a terminal, make new-plugin asks for what's missing:
    make new-plugin ARGS='--provider acme --name Acme --source api --kind notices --reader feed --url https://acme.example/changelog.xml'
  2. Fill in every TODO(new-plugin) in providers/acme/: the reader, the provider and source metadata in provider.go, a saved copy of the source in testdata/, and "Why this source" in README.md. Then write the golden file and read it like code:
    go test ./providers/acme -run TestApi -update
  3. Check it the way CI will, and open the PR (git commit -s, one provider per PR):
    make check

More

About

How patch-it notices when something your code depends on changes: APIs, packages, SDKs, runtimes, CI, AI models. You get the fix, not the alert.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages