Automate the release workflow using GitHub actions
commit290ea73da0bf2b8df7bddcb78a7c73c52929c96c
authorAndreas Gohr <andi@splitbrain.org>
Thu, 23 Feb 2023 14:03:01 +0000 (23 15:03 +0100)
committerAndreas Gohr <andi@splitbrain.org>
Fri, 24 Feb 2023 20:45:12 +0000 (24 21:45 +0100)
tree26d48bc3bb87791bd3a504097ea2379d3dcbdafa
parenta42c05d2dd170bfdf65b34862ce9ed085297d733
Automate the release workflow using GitHub actions

This introduces a two-part release mechanism. A manually triggered
workflow asks for the important info like type of release (stable, rc)
and code name. It then creates a cleanly mergable pull request.

When that pull request is merged, a release is automatically tagged,
built and uploaded.

Another workflow is introduced to keep track of the deleted.files info.
This is one less chore to do on a release.

A new scheme for tags is also introduced, making all tags sortable,
regardless of their type. They follow the pattern

release-YYYY-MM-DD(<hotfixletter>|rc)

A script will be used to clean-up the existing tags.
.editorconfig
.gitattributes
.github/release.php [new file with mode: 0644]
.github/version.php [deleted file]
.github/workflows/deletedFiles.yml [new file with mode: 0644]
.github/workflows/release-build.yml [new file with mode: 0644]
.github/workflows/release-preparation.yml [new file with mode: 0644]
.github/workflows/release.yml [deleted file]