Skip to content

Build automation #19

@jfretheim

Description

@jfretheim

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions