opened
sideeffffect
username_0
Allows the user to choose certain branches, where a stable version of the artifact will be published on every push (i.e. not only when on a tag).
This is suitable, for example, in a continuous publishing/deployment scenario.
Enable opt-in publishing release from certain branches even when not on tag
issue
created
olafurpg
username_1
Thank you for this contribution! I'm curious if it's possible to achieve similar functionality with the following steps in CI?
```sh
git tag -af $(git describe) -m $(git describe)
sbt ci-release
```

I would prefer to try and keep this plugin as simple as possible.
comment
created
sideeffffect
username_0
...
[info]  1.5.3-5-g5e98230
```
Then it "works". But it's quite hacky :disappointed: . People probably won't like the `g` and would like `+`, so that the version would look the same as if produced by `sbt-dynver` in a normal way.

Another advantage of doing this in `sbt-ci-release` (over manipulating with git from the outside), is that you don't need to touch git yourself at all. All you need is `sbt-ci-release` and do the configuration in sbt.
comment
created
olafurpg
username_1
You can BTW avoid the `+` character with `dynverSeparator in ThisBuild := "-"`. The `MatchError` looks like a bug in sbt-dynver. I encourage you to report an issue to sbt-dynver so that the version number can be configured. Alternatively, you can set the version yourself with `version in ThisBuild := "..."`

I'm gonna close this PR since I'm not convinced the benefits outweigh the added complexity in this plugin. You can always fork the repo and release under another organization, `CiReleasePlugin.scala` is less than 200 lines of code anyways.
comment