From f7eca8f785b7460fced88703e5cc08d4695db3e9 Mon Sep 17 00:00:00 2001 From: Bryan Haberberger Date: Fri, 12 Jun 2026 12:50:33 -0500 Subject: [PATCH] Track production/development deploys via GitHub environments Add 'environment: production' to the cd_prod deploy job and 'environment: development' to the cd_dev deploy job so each real pm2 deploy registers a GitHub Deployment (active on success, prior auto-inactivated), matching how TPEN-services tracks deployments. --- .github/workflows/cd_dev.yaml | 1 + .github/workflows/cd_prod.yaml | 1 + 2 files changed, 2 insertions(+) diff --git a/.github/workflows/cd_dev.yaml b/.github/workflows/cd_dev.yaml index 0630e36..1f678ae 100644 --- a/.github/workflows/cd_dev.yaml +++ b/.github/workflows/cd_dev.yaml @@ -58,6 +58,7 @@ jobs: needs: - merge-branch - test + environment: development strategy: matrix: node-version: diff --git a/.github/workflows/cd_prod.yaml b/.github/workflows/cd_prod.yaml index 2244a17..cbee223 100644 --- a/.github/workflows/cd_prod.yaml +++ b/.github/workflows/cd_prod.yaml @@ -22,6 +22,7 @@ jobs: deploy: needs: - test + environment: production strategy: matrix: node-version: