uses the "development" environment during dev deployment#669
Merged
Conversation
use separate environments to manage different secrets (e.g. different API endpoints)
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Connect publish GitHub Actions workflows to support using a separate GitHub Environment for dev deployments, enabling different secrets (for example, different API endpoints) between dev and production.
Changes:
- Replace the manual workflow’s environment option from
new-productiontodevelopment. - Update the dev deployment workflow to call the reusable publish workflow with
environment: development.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/connect-publish-manual.yaml | Updates workflow_dispatch environment choices to include development. |
| .github/workflows/connect-publish-dev.yaml | Switches the dev deployment to use the development GitHub Environment when invoking the reusable workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
8
to
+14
| publish-production: | ||
| name: "Publish (to production server)" | ||
| uses: ./.github/workflows/connect-publish-manual.yaml | ||
| with: | ||
| namespace: "dev" | ||
| inputs_data_version: "dev" | ||
| environment: "production" | ||
| environment: "development" |
matt-dray
approved these changes
May 20, 2026
Contributor
matt-dray
left a comment
matt-dray
left a comment
There was a problem hiding this comment.
Ah gotcha, thanks for recognising and updating.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
use separate environments to manage different secrets (e.g. different API endpoints)