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
When a deploy build is triggered, the heroku website could be packaged and deployed following these instructions.
Solution
When a tagged version is pushed to aide_design_specs or when pushes are made to the stable branch (up to the implementer which solution is preferred, here is are examples of tagged versions and stable branches starting workflows.
A GitHub action can be configured to deploy to Heroku. A Heroku token will likely have to be added to the repo secrets for this to work.
Alternatives
The website is currently deployed manually from the command line by AIDE team members. An alternative is to mimic this deployment in a custom GH action.
Use Case
When a deploy build is triggered, the heroku website could be packaged and deployed following these instructions.
Solution
When a tagged version is pushed to
aide_design_specs
or when pushes are made to thestable
branch (up to the implementer which solution is preferred, here is are examples of tagged versions and stable branches starting workflows.A GitHub action can be configured to deploy to Heroku. A Heroku token will likely have to be added to the repo secrets for this to work.
Alternatives
The website is currently deployed manually from the command line by AIDE team members. An alternative is to mimic this deployment in a custom GH action.
From the above instructions.
The text was updated successfully, but these errors were encountered: