Improve CI

[micwoj92]

I think that the CI is pretty bad, I have been working a bit on improving it but I don't know Windows/Powershell that much and I hope that due to this project's popularity someone who knows better will see it.
So couple of points I think are worth improving:

• Use more (GitHub provided) variables so the CI is more flexible (example ${{ github.repository }} which is used now)

• Change manual git clone to actions/checkout (it's pretty easy, but for some reason not always as reliable)

• Change manual autoit download+install to use some package manager (or just a faster/better/more elegant way, I tried chocolatey and it worked but was very slow, scoop worked much better, but with pretty small size of autoit tools and the fact that first you need to get scoop itself I don't know if it brings any time benefits)
  ^ Caching is used now

• Remove the ugly (in my opinion) need for Start-Sleep -s 10. This is "because it returns back to shell before it completes". and by "it" I mean the autoit compiler/tools. I tried different methods, for example loop that checks if file exists but it either hanged the GitHub runner or was really slow (and still needed wait command anyway). Again, I might be missing something obvious here.

• Print hash of produced binary (and then use it in release)

• Automatically upload artifacts on release.

[sanny-io]

Linking this related comment here.

#20 (comment)

[micwoj92]

Ok, this should be easy (besides that automation part) but it is up to Robert to change his workflow. Thanks for suggestion.

[micwoj92]

@rcmaehl Will next release be artifact from CI? Then it would solve 1st point.

[rcmaehl]

@rcmaehl Will next release be artifact from CI? Then it would solve 1st point.

I mean.... It can be.

[micwoj92]

Thanks, then it also needs to include new x86 build + hashes for it.