2200 introduced a reusable Appetize build action. As discussed, we should add a deployment-level github action that calls this reusable action to deployments that require building to Appetize.
As described in my latest comment on #2200, some manual steps are required to set up the Appetize app instance. I have completed these steps for the plh-teens-app-tz-content deployment: I have added an organisation-level secret, APPETIZE_TOKEN, plus a repo-level secret, APPETIZE_APP_KEY. That should be sufficient for running the action from that repo.
The app is available on appetize currently (built from master code branch and main content branch) here.
What?
2200 introduced a reusable Appetize build action. As discussed, we should add a deployment-level github action that calls this reusable action to deployments that require building to Appetize.
As described in my latest comment on #2200, some manual steps are required to set up the Appetize app instance. I have completed these steps for the plh-teens-app-tz-content deployment: I have added an organisation-level secret,
APPETIZE_TOKEN, plus a repo-level secret,APPETIZE_APP_KEY. That should be sufficient for running the action from that repo.The app is available on appetize currently (built from
mastercode branch andmaincontent branch) here.