From 627031094b72734e69289d2479447e971d408c39 Mon Sep 17 00:00:00 2001 From: Bryan Haberberger Date: Fri, 12 Jun 2026 12:50:41 -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 c11bb8e..cb449c8 100644 --- a/.github/workflows/cd_dev.yaml +++ b/.github/workflows/cd_dev.yaml @@ -33,6 +33,7 @@ jobs: if: github.event.pull_request.draft == false needs: - test + environment: development strategy: matrix: node-version: diff --git a/.github/workflows/cd_prod.yaml b/.github/workflows/cd_prod.yaml index 09a685c..3228697 100644 --- a/.github/workflows/cd_prod.yaml +++ b/.github/workflows/cd_prod.yaml @@ -33,6 +33,7 @@ jobs: run: npm run coverage:ci deploy: needs: test + environment: production strategy: matrix: node-version: