hdevalke
hdevalke
It could be added under a feature completions. and be implemented using the subcommand completions with`--shell` as option if it could not be autodetected by parsing the SHELL env variable.
As we use the semver crate to parse semantic versions, the version number has to be a valid semver. (see ) What you describe is known as [CalVer](https://calver.org/), but different...
I once made my own parser but never used it. I repushed the branch for reference. To make it lenient this line should change https://github.com/convco/convco/blob/custom-semver/src/semver.rs#L248. However parsing it lenient would...
Not yet. There is still one issue I would like to fix before releasing the next version. Probably this weekend.
Yes indeed
Thank you for the pull request and the idea. However, when multiple commits are added, this would create jumps in the pre-release numbering. > Tagging commits on a feature branch,...
I have no experience in writing a github action and how to make it compatible with different OSes and architectures. Can you also describe how you would like to use...
No problem I will try to make something when I find time. Thank you for liking convco.
I tried to create an action. https://github.com/marketplace/actions/convco Would you be able to try it out and give feedback?
I updated the action so it only installs convco. You should be able to use this: ```yaml - name: Convco install uses: convco/[email protected] ```