Skip to content

Staging to Production - #19

Merged
susrisha merged 23 commits into
productionfrom
staging
Jul 23, 2026
Merged

Staging to Production#19
susrisha merged 23 commits into
productionfrom
staging

Conversation

@susrisha

Copy link
Copy Markdown
Collaborator

Staging to production deployment

susrisha and others added 23 commits July 1, 2026 15:22
Deployment workflow for testing environment
## What

Adds automatic deployment triggering when a pull request is merged into `develop`, `staging`, `production`, or `testing`. Only the workflows whose code actually changed are triggered — a frontend-only PR deploys just the frontend, a backend-only PR deploys just the backend, and a PR touching both deploys both in parallel.

## Changes

- **New workflow `trigger-deploy-on-merge.yml`**
  - Runs on `pull_request: closed` against `develop`, `staging`, `production`, and `testing`; proceeds only if the PR was actually merged (not just closed).
  - Maps the target branch to the environment name the deploy workflows expect (e.g. `develop` → `development`).
  - Uses `dorny/paths-filter@v3` to detect whether the merged PR changed `backend/**` or `frontend/**` (each deploy workflow's own file is included in its filter).
  - Calls the matching deploy workflow(s) as reusable workflows with `secrets: inherit`.
Trigger deployments automatically on PR merge, scoped to changed code
Changes the input parameters and the production branch
Sample change to check leadboard deployment
Changed workflow trigger to gh client
Minor change to test backend deployment
Fix the error with deployment
@susrisha
susrisha merged commit a3c3329 into production Jul 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants