You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Artifacts should match our release format, which includes version number
On tag creation, a pipeline should kick off matching the below format, which will then be used as the assets in question (automatic release is possible, bonus to look into that - this repo for example has this working - GitHub Actions performs the release on tag)
For PR artifacts that are non-releases / non-tagged, the short commit hash should be included
Optional: drop the matrix style pipeline for Windows, I don't think we need debug to run in CI.
Note: On releases we directly upload the unzipped AppImage as there is no compression savings. this can be ignored if we can't directly push as an AppImage
Artifacts should match our release format, which includes version number
debug
to run in CI.Note: On releases we directly upload the unzipped AppImage as there is no compression savings. this can be ignored if we can't directly push as an AppImage
Current format
Planned Format
Release/Tagged format:
PR / Non-release format, assuming the last commit is
e8ea2b3
:The text was updated successfully, but these errors were encountered: