-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: make repo, user and branch url safe #289
Conversation
@BetaHuhn Could we get your eyes on this? |
|
This PR is not stale. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Thank you :) |
* fix: slugify repo and branch * chore: linting * fix: param case user * chore: comment * chore: comment * chore: formatting * feat: output unique deployment url * fix: get deployment url with protocol * feat: handle long branch urls * feat: add logging * chore: debug * feat: logs * fix: must be 63 chars * fix: b64url * fix: b64url * fix: digest to hex * chore: info to warning * chore: remove editorconfig and prettier file * chore: update lockfile * chore: add back action-input-parser * chore: improve regex * chore: cleanup --------- Co-authored-by: Josh Barr <[email protected]>
🎉 This PR is included in version 1.10.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This is a revival of #184
This PR makes sure that the params repo, user and branch are url safe, due to problems explained in the original PR. I used https://perishablepress.com/stop-using-unsafe-characters-in-urls as a source of what's URL safe and what's not, and then added an inverted regex to only keep relevant characters.