Alessandro Chacón
Alessandro Chacón
Hey @AlexJupiter , not at the moment. Probably up next. I'll remove it from In progress meanwhile
Nope, let's remove it.
@DiyanDev it seems like --release-version is broken since recently, that seems to be the reason for the feature request. I actually does the tagging even with the argument.
Actually, it happens to me even without the --dry-run. Or maybe I don't understand how it would work. `~$ git tag 1.0.0 1.0.0-35 1.0.0-39 1.0.1 1.0.2 1.0.3 1.1.0 1.1.0-0 ~$...
it seems like the tag "1.1.1-0" is always wrongly created. Maybe this is a different issue and not related, but it seems like the --release-version is having side-effects, but the...
it seems like npx release-it --release-version actually fetches the tags from the origin, which was unexpected to me. You can ignore my comments.
Can we also in this issue: 1. Change the name of the folder to a better name ? 2. ~~Integrate (or reference) GUI and contract README ?~~ 3. Remove old...
4. Modify README accordingly
Looks amazing