-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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: massage release notes links #17636
fix: massage release notes links #17636
Conversation
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
|
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.
I like this idea, but there's a problem. 😉
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
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.
otherwise LGTM
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
added more description. |
It looks like your PRs have been spamming pnpm, Eg pnpm/pnpm#5071 Has this been fixed? |
yes |
I've labeled this PR as large impact, because if there's any mistake or misunderstanding here with this parsing then it could result in mass backlink spam. I'm not sure of the best way to monitor for this problem in production though because I'm not aware of any github.com search we can do to find our own backlinks. i.e. in a worst case scenario we could be backlink spamming for hours or days before we annoy someone enough to report it. |
I have checked the fix on a real repository. Also, I added new unit tests to make sure that the URLs in release notes use |
…ug/matchAll-in-collectLinkPosition-function-ignores-colors
${'https://github.com/foo/bar/discussions/1#comment-123'} | ${'[https://github.com/foo/bar/discussions/1#comment-123](https://togithub.com/foo/bar/discussions/1#comment-123)'} | ||
${'https://github.com/foo/bar/issues/1#comment-123'} | ${'[https://github.com/foo/bar/issues/1#comment-123](https://togithub.com/foo/bar/issues/1#comment-123)'} | ||
${'https://github.com/foo/bar/pull/1#comment-123'} | ${'[https://github.com/foo/bar/pull/1#comment-123](https://togithub.com/foo/bar/pull/1#comment-123)'} | ||
${'github.com/foo/bar/discussions/1'} | ${'[foo/bar#1](togithub.com/foo/bar/discussions/1)'} |
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.
do those short links also work for discussions?
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.
the answer is yes, but i will close this PR too and refactor it
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.
#17819 is doing this refactor, this PR is an aftermath for just one case
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
closing this as maroon is no longer working on it, opened #18944 instead |
Changes
added new regex to massage
What's Changed
andNew Contributors
in release notes.before the fix, these sections did not add a link to the user's profile, and the PRs links have been displayed incorrectly.
What's Changed
andNew Contributors
sections in the PRs below:Before the fix:
Update pnpm to v7.6.0 - before fix MaronHatoum/16921#43
After the fix:
Update pnpm to v7.6.0 - after fix MaronHatoum/16921#48
Context
closes #17404
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: