Think this is what you wanted @trojanobelix when you wanted binary to be available directly for testing
This will make releases when a tag starting with v*.*.* is pushed.
if it is v(number).(number).(number), like v.1.2.3 it is a release, but if it something like v1.2.3[not numbers] like v1.2.3-rc4 it is pre-release
When it makes (pre)release it attach the binary as a attachment
Think this is what you wanted @trojanobelix when you wanted binary to be available directly for testing This will make releases when a tag starting with
v*.*.*is pushed. if it is v(number).(number).(number), like v.1.2.3 it is a release, but if it something like v1.2.3[not numbers] like v1.2.3-rc4 it is pre-releaseWhen it makes (pre)release it attach the binary as a attachment
you can see the result on the last 2 releases on my test repo: https://github.com/nimrof/CANopenEditor_gh_test
Not related to this, but you also have binary attached to all pr. under the checks tab (its a little hidden)