feat: :sparkles: added new DEPLOYMENT_ENVIRONMENT input param for the action
The new DEPLOYMENT_NAME input parameter was added for the action. This param is responsible for the custom name of the GitHub Deployment
Why are these changes added?
I have a monorepo with several static sites, that I deploy to the Cloudflare Pages. When I create a Preview for them all, they have the same name — preview, and only the last deployed Site is available through the Deployment panel.
With the changes from this PR, I could:
- set a custom name for my deployments
- all deployments will be available with the deployment panel in the PR
View words about the previous action
The pages-action has another solution for the problem. I think that the input parameter is a better solution because gives more flexibility for naming
Amazing feature, would be nice to get it merged. My use case is the frontend deployed via Pages to dev and prod workers. Both of them have GitHub deployments with the title 'production', which is confusing
@Maximo-Guk can we get this merged please?👍
Any update from maintainers on getting this merged? I have three sites in a monorepo and quickly getting the preview URLs for each site if they all get updated is slightly annoying :(