fix!: Distinguish between "Pleo" env and Github env in deployment #267
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.
Fixes the following deploy error https://github.com/pleo-io/product-web/actions/runs/11483548110/job/31959328063
Currently it is expected that the name of Github environment we deploy to matches one of the "Pleo" environments as we define them in the Environment type
This is problematic for the spa-config-inject script which uses the name of the Github environment to find the appropriate config file.
We can't deploy multiple apps from one repo to the same Github environment.