Currently, committers must keep the assembled .mez file up to date along with any code changes.
A better solution would be a Github action that creates these artifacts.
Some options for a Github action:
- build the artifact and commit it back the branch
- remove the
.mez file from the repository altogether and point interested parties to artifacts created by the action. Additionally, tagged releases could be created on PR merge.
Currently, committers must keep the assembled
.mezfile up to date along with any code changes.A better solution would be a Github action that creates these artifacts.
Some options for a Github action:
.mezfile from the repository altogether and point interested parties to artifacts created by the action. Additionally, tagged releases could be created on PR merge.