Add command line input for tag management

[andreaTP]

Added command line arguments to pass default parameter on tagRelease Step.

[andreaTP]

maybe @jroper @gseitz or anybody else can comment here?

[jroper]

I'm not 100% sure of what the use case is here, nor do I 100% understand how the tag-default attribute is used, could you explain a little more?

[jroper]

It would be good to see this option documented in the README.

[jroper]

I don't understand this scripted tests - why does release with defaults fail and release with-defaults tag-default a also fail, but release with-defaults tag-default o doesn't fail? What's so special about o that makes it different to a? I just don't get it. Could you add some comments here to explain what's being tested and what's going on?

[andreaTP]

going to add comments around.

[xuwei-k]

-      (Space ~> token("tag-default") ~> Space ~> token(StringBasic, "<next version>")) map ParseResult.TagDefault
+      (Space ~> token("tag-default") ~> Space ~> token(StringBasic, "<tag default>")) map ParseResult.TagDefault

[andreaTP]

right thanks

[andreaTP]

TL;DR
Just let user adjust hardcoded default of the tagging step

Rationale
The usage of this parameter is explicitly for usage on CI, release with-default alone doesn't let me decide the rules for tagging explicitly, and the only default is the hardcoded abort.
With this PR you will be able to pass through command line arguments different tagging default.
My specific use case is that I want to overwrite SNAPSHOT tags on git, but this enable also the user to give personal tags through the argument in CI.

[andreaTP]

done fixes and addressed comments.
rebased modifications.

Thanks for taking care and for comments :-)

[andreaTP]

CI failure looks spurious to me

[jroper]

Ah, I get it now. Perhaps then a more descriptive name would be default-tag-exists-answer. Also, the description of the value used in the parser should probably be o|k|a, rather than <tag-default>.

Also, this needs to be documented in the README, eg, in the section about with-defaults, saying that the answer to the existing VCS tag prompt can be overridden using the default-tag-exists-answer argument.

[andreaTP]

Done, thanks a lot for the feedback! :-)

[andreaTP]

Thanks!

[andreaTP]

Due to recent updates, could you please publish a release?
Thanks in advance