deploy-parakh-dev.yml triggers on dev only. There is no automated deployment of the ParakhAI frontend to prod.
Scope
Follow the pattern already working in DataSpaceFrontend/deploy-Dataspace.yml, which handles both environments in one workflow:
environment: ${{ github.ref_name == 'main' && 'production' || 'development' }}
- trigger on
main for prod
- deploy a digest-pinned build, not a moving tag
- gate on smoke tests before promoting
- automatic rollback on failure, run still reporting red
Reference
The smoke-gated promote/rollback structure in deploy-Dataspace.yml is the closest working model — its promote-dev job only runs once smoke tests pass, and rollback-dev restores the previous release otherwise.
deploy-parakh-dev.ymltriggers ondevonly. There is no automated deployment of the ParakhAI frontend to prod.Scope
Follow the pattern already working in
DataSpaceFrontend/deploy-Dataspace.yml, which handles both environments in one workflow:mainfor prodReference
The smoke-gated promote/rollback structure in
deploy-Dataspace.ymlis the closest working model — itspromote-devjob only runs once smoke tests pass, androllback-devrestores the previous release otherwise.