Please "git tag" your RAKU modules with it's versions

[AntonOks]

Can you please "GIT TAG" your RAKU modules with it's version, similar and at the same time you maintain it's "version": "x.y.z" in your META6.json file?

I was told, this will happen "for free" going forward with mi6 anyhow, but for now it would be great if you spend those 2 seconds already now :)

"Tagging" is generally highly appreciated in regards to "reproducible builds" and here especially for the "Rakudo Star" modules

THANK YOU!

[grondilu]

I'm not familiar with git tag. Feel free to paste a command line that I'm supposed to enter.

[AntonOks]

I'm not familiar with git tag. Feel free to paste a command line that I'm supposed to enter.

git tag <your tag string> will add a "tag" pointing to the commit you are currently "in" (so checked out ;) )

As your META6.json say's you are on "version" : "1.0.0", it would make sense to "tag" it with the same version ;)

1. To tag your current HEAD commit, just run git tag 1.0.0.
2. If you would like to add a tag to a former commit, like in your case, where you seem to have changed your META6.json to version 1.0.0, which seems was done in commit d281107, you can run: git tag 1.0.0 d281107

You can later show the tag's infos as with any other commit: git show 1.0.0 and/or delete it with git tag -d 1.0.0

[grondilu]

The thing is, I really dislike how versioning currently works. I don't like having to pick a version number every time I commit, so I'm not very eager to add any step to my workflow.

[AntonOks]

The thing is, I really dislike how versioning currently works. I don't like having to pick a version number every time I commit, so I'm not very eager to add any step to my workflow.

general software development rules (nothing to do with RAKU and friends):

• you don't have to "git tag" everything you commit.
• you should use "git tag" to highlight that some commits are "special", like which "released software version" is based on which commit

RAKU specific:

• ZEF and friends require a RAKU developer to maintain a "version" flag in the META6.json

---

back to my requests / this discussion... sooner or later, there will be only "tagged" modules allowed within "Rakudo Star" (maybe even in Rakudo in general, but this is not my decision / topic, see the "mi6" hint in my first posting)... latest them your module would have to be removed out of "Star", which may be a pity

[grondilu]

Hopefully someone less lazy than me takes ownership of this module and maintains it properly. I like writing raku code but even maintaining a META6.json file is a hassle for me.

[AntonOks]

you can give me admin permissions on this repo and I'll ad a tag...

[AntonOks]

thanks