After a successful CI run on a PR to dev or master, all assets need to be pushed to the dedicated release on github.
NOTE: Initially, only screenshots will be bundled and posted to the releases on Github since executables are being cryptographically signed in the CI pipeline and should only be pushed to private repositories which we don't have for this project.
Approach WIP
if comment matches the semver pattern MAJOR.MINOR.PATCH[-PRERELEASE] and the comment is not yet used as a tag
intended_tag = comment concat meta(build type, date, ref) → resulting to e.g. 2.1.2-beta+ios.20130313144700.5114f85
create a Github release w/ intended_tag
if PRERELEASE set as prerelease
push related assets to release
Our merging approach will require naming our merging appropriately in order to trigger automated release generation. As long as the merge comment complies to the semver pattern exclusing the META clause, a release build should be executable.
Problem
After a successful CI run on a PR to
devormaster, all assets need to be pushed to the dedicated release on github.Approach WIP
MAJOR.MINOR.PATCH[-PRERELEASE]and the comment is not yet used as a tagintended_tag= commentconcatmeta(build type, date, ref) → resulting to e.g.2.1.2-beta+ios.20130313144700.5114f85intended_tagOur merging approach will require naming our merging appropriately in order to trigger automated release generation. As long as the merge comment complies to the semver pattern exclusing the META clause, a release build should be executable.
References