Meanwhile, I’m finally getting back to posting to report on a fun thing you can now do with your PGXN distributions. Thanks to the Version Badge service from the nice folks at Gemfury, you can badge your distributions! Badges look like this:
]]>Meanwhile, I’m finally getting back to posting to report on a fun thing you can now do with your PGXN distributions. Thanks to the Version Badge service from the nice folks at Gemfury, you can badge your distributions! Badges look like this:
You’ve no doubt seem similar badges for Ruby, Perl, and Python modules. Now
the fun comes to PGXN. Want in? Assuming you have a distribution named
pgfoo, just put code like this into the README file:
[](https://badge.fury.io/pg/pgfoo)
This is Markdown format; use the syntax appropriate to your preferred README format to get the badge to show up on GitHub and PGXN.
That’s it! The badge will show the current releases version on PGXN, and the button will link through to PGXN.
Use Travis CI? You can badge your build status, too, as I’ve done for pgTAP, like this:
[](https://travis-ci.org/theory/pgtap)
Coveralls provides patches, too. I’ve used them for Sqitch, though I’ve not yet taken the time figure out how to do coverage testing with PostgreSQL extensions. If you have, you can badge your current coverage like so:
[](https://coveralls.io/r/theory/sqitch)
So get badging, and show off your PGXN distributions GitHub and elsewhere!
]]>