hdevalke
hdevalke
> Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE) Not implemented as not in...
Sorry to answer late, but i don't have much free time. I see indeed that it does not do what is expected. ```sh #!/bin/env sh set -x rm -rf .git...
I think that in this case the issue is that there is no commit that increments the version by convention. Maybe in this case, there should exit with an error,...
For point 7 I cannot reproduce. Which version of convco do you use @kaankoken ? ``` #!/bin/env sh set -x rm -rf .git convco version git init . convco version...
Thanks for your input. This is more about releasing convco itself then releasing applications using convco. It is not the goal to add a `convco release` sub command. The main...
A manual workflow has been added to trigger a release. It does run cargo-release and creates a new tag (0.5.1 has been released this way) However, the build binaries workflow...
closed with d91b92acc071a0f8e4de1400945158edb88b2184
The docker image already contains statically linked binaries. You should be able to use `COPY --from=..` in your Dockerfile. The binary in the convco image is `/entrypoint`.
Indeed a new issue can be opened if this feature is still wanted.
The code completions are available here: https://github.com/convco/convco/releases/tag/v0.5.1 Depending on how you install convco code completions will be available e.g. `brew install convco` will also install the completions