Add environment to branch-deploy parameters. #95
Conversation
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
kevinbackhouse
requested review from
JarLob,
Kwstubbs,
m-y-mo,
p- and
sylwia-budzynska
as code owners
Copilot finished reviewing on behalf of
kevinbackhouse
November 25, 2025 10:04
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes an issue where the smoke test workflow was creating deployments named "production" instead of "smoketest". The fix explicitly sets the environment parameter in the branch-deploy action configuration.
- Adds the
environment: "smoketest"parameter to the branch-deploy action inputs to ensure deployments are created with the correct environment name
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The smoke test workflow is still creating a deployment named "production", even after #92. Maybe this will work.