Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Build automation #19

Open
jfretheim opened this issue Aug 9, 2024 · 0 comments
Open

Build automation #19

jfretheim opened this issue Aug 9, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jfretheim
Copy link
Contributor

jfretheim commented Aug 9, 2024 •
edited
Loading

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:

  1. build the artifact and commit it back the branch
  2. 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.
@jfretheim jfretheim added the enhancement New feature or request label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jfretheim