@jason-yeo-paidy I now have merge rights in this repo. And yes, we would love to have help here. If you send PRs, I can merge them. You can also comment on existing PRs and suggest they be merged.

Note that because of the Bintray shutdown, we cannot currently publish this plugin. So the most immediate need here is a pull request that replaces sbt-bintray with sbt-ci-release. (You might see what happens at sbt/sbt-projectmatrix#47 and copy it. And/or, there might be other sbt/* plugin repos that already have the right stuff, I haven't looked.) see #185

About CI, currently we are on Travis-CI. We could continue using that, or move to GitHub Actions, either way is fine. see #184

You can check out https://github.com/sbt/sbt-pgp/tree/develop/.github/workflows for the reference implementation of how to hook up GitHub Actions.

I think sbt-git has been abandoned because it's no longer in fashion to use it among the core developers in sbt or sbt plugin community. sbt modules use https://github.com/dwijnand/sbt-dynver.

re: GitHub Actions, I've opened a separate help-wanted tickets at #184 (CI) and #185 (publishing via sbt-ci-release)

@raboof's efforts to publish, at #188, seem to have stalled

@raboof's efforts to publish, at #188, seem to have stalled

Actually 1.0.1 was released from CI :)

I'm going to close this, since we have a relatively recent release.

See also my recent remarks on #168.

Help with reviewing PRs, triaging issues, and such, remains welcome from anyone who cares to participate.

Personally, I can't afford to become knowledgeable about the specifics of this plugin, but I can hit "merge" when it looks like a panel of volunteers has agreed that something is mergeable.

Eugene or I can also grant maintainer rights. The way that usually works is for someone to first demonstrate their interest and ability over some period of time, by wading in with reviews, triaging, and such.