Publish binaries from latest build action to release tag "volatile"
TG9541 opened this issue · 1 comments
TG9541 commented
Sometimes it would be nice to just have those artifacts...
TG9541 commented
It's maybe not the most obvious way to do it but I decided "attach" the release info in the build step at the end of forth.asm
. That way all release artifacts files contain version information, one way or the other:
stm8ef-bin.tgz and stm8ef-bin.zip in forth.asm
:
; ##########################################
; # Release info added by GitHub action:
; # repository: TG9541/stm8ef
; # branch name: refs/heads/master
; # sha: 8ee3453ce577181ef5e9bddda94f56d448dbf962
; ##########################################
stm8ef-rst.tgz in any forth.rst
file:
4148 ; ##########################################
4149 ; # Release info added by GitHub action:
4150 ; # repository: TG9541/stm8ef
4151 ; # branch name: refs/heads/master
4152 ; # sha: 8ee3453ce577181ef5e9bddda94f56d448dbf962
4153 ; ##########################################
That way it's easy to distinguish a copy of forth.asm
from a release archive from a version controlled development file.