Work through the extensions gist and select 50–100 extensions on GitHub. Submit pull requests to add a GitHub workflow to each that publishes the extension on PGXN on release. Some criteria to select extensions:
Some activity in the last couple years
Already on PGXN or has a META.json, or just looks useful
Uses the PGXS build pipeline (PGRX and others are okay too, but the client only does PGXS and Configure)
Responsive developers (look at issues and PRs)
The contents of the PRs should be:
A META.json and automate versioning
A .gitattributes file to exclude non-distributable files from git archive
A Makefile target to build a distribution (handy for making sure it actually works)
A GitHub Workflow using pgxn-tools to automate release
Optionally: A GitHub Workflow using pgxn-tools to test on all supported Postgres versions
Work through the extensions gist and select 50–100 extensions on GitHub. Submit pull requests to add a GitHub workflow to each that publishes the extension on PGXN on release. Some criteria to select extensions:
The contents of the PRs should be:
META.jsonand automate versioning.gitattributesfile to exclude non-distributable files fromgit archiveMakefiletarget to build a distribution (handy for making sure it actually works)Some example PRs:
Makefiletargets)