varlesh
Workflow for creating GH releases with compiled themes
I just set up a workflow for your repository to create releases containing the .tar.gz-files for every cursor theme.
The release would be automatically generated any time you create a tag on some commit. That way you can decide which commits warrant their own releases.
Also, I added a little fix for your Makefile, which was necessary to use the VERSION-variable in that make-case.
I hope that this is useful to you, because it enables me/others to find a compiled version of these icons that isn't on Pling (where they force people to manually load the latest files, prevent any scriptable access, afaict).
I made sure that this wouldn't cost you anything to deploy, as long as the repository is public.
Lastly, to give you an idea, my tests on the GH-hosted runners ran for <10 minutes each time. (I cleaned up, but I think I'll add another tag to enable you to see for yourself on my fork.)
Hope that clears up any questions, and that you find this to be a sensible contribution to your project.
If not, please let me know, if you have any concerns with me keeping my public fork going and periodically building my own releases. (I'd like to keep it public to not incur any bills for it. ;) )
@varlesh Looks good for me. You may merge it if you want to support the GitHub releases
