Vasil Vasilev

> Assuming that the user wants -SNAPSHOT releases for their branch pushes, but NO ci release for their tag pushes, we just need to add a conditional I just realized,...

Ah but not really? ``` - name: Import signing key if: env.GITHUB_REF_TYPE == 'tag' run: echo $PGP_SECRET | base64 -d | gpg --import ``` This wouldn't run for hash releases.

Which means that `sbt-github-actions` needs to know about the setting...

> Assuming that the user wants `-SNAPSHOT` releases for their branch pushes, but NO ci release for their tag pushes, we just need to add a conditional: > > ```yaml...

I mean, as a stopgap, the `release` step can be behind a condition, and that one is here.

> It'll be a bit confusing in the UI to see an empty publish job succeed, but otherwise a good idea! This is how `sbt-github-actions` works out of the box....

How does releasing snapshots without releasing tagged releases work currently? What's the discriminator?

@armanbilge Can you maybe take this for a spin? I will release a `SNAPSHOT`. 😉

```scala addSbtPlugin("io.vasilev" % "sbt-spiewak-sonatype" % "0.23-11-6c79539-SNAPSHOT") ``` and you need the snapshots resolver for the new `s01.oss.sonatype.org` host, fyi. ```scala resolvers += "Sonatype OSS Snapshots" at "https://s01.oss.sonatype.org/content/repositories/snapshots" ```

The `fs2` case (and the default): Settings: ```scala enablePlugins(SonatypeCiReleasePlugin) ThisBuild / spiewakMainBranches := Seq("main") ThisBuild / spiewakCiReleaseSnapshots := true ThisBuild / spiewakCiReleaseTags := true ``` Output: ```yaml publish: name: Publish...