-
Notifications
You must be signed in to change notification settings - Fork 50
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: support trailing slash #120
Conversation
Not sure why lint is complaining... If I remove the |
It's complaining because you're backslash-escaping it in a string. You don't need to backslash-escape a slash character in a string, only in a regex literal. |
Co-authored-by: Rich Trott <[email protected]>
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.
Looks good to me. I assume that since you're a releaser, you've taken into consideration whether this might break relevant tools like the changelog maker. (I don't imagine it would break those tools. I'm just mentioning it in case you or someone else who deals with that tooling more often might think otherwise or want to give it a bit more consideration/testing.)
Considering we are not dropping support but adding trailing slash support, it should not impact the existing release workflow or tools like changelog maker. But, I'll monitor it over the week. |
I think the one possible change in behavior might be branch-diff if the PR-URL in the commits being compared differed only in whether they ended in a slash or not (since they'd no longer match). |
That's correct. Let me see this first. |
Created nodejs/branch-diff#70 |
Refs: https://openjs-foundation.slack.com/archives/C019Y2T6STH/p1720463991463229