feat: ✨ added new DEPLOYMENT_NAME input param for the action #355
Conversation
This file contains 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
VoloshchenkoAl
force-pushed
the
feat/add-deployment-name
branch
from
63e97e2 to
f940b70
Compare
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.
The new
DEPLOYMENT_NAMEinput parameter was added for the action. This param is responsible for the custom name of the GitHub DeploymentWhy 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:
View words about the previous action
The
pages-actionhas another solution for the problem. I think that the input parameter is a better solution because gives more flexibility for naming