-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
GitHub release changelog number misinterpreted as issue reference #16455
Comments
how about No.218? |
How about we strip it off? It makes sense to have it on https://rust-analyzer.github.io/thisweek/2024/01/29/changelog-218.html, but not on the GitHub Releases page. |
Is the related setting here? rust-analyzer/xtask/src/release/changelog.rs Lines 82 to 84 in e4146af
|
No, it's around rust-analyzer/xtask/src/publish.rs Lines 10 to 11 in e4146af
The code you linked to generates a changelog ASCIIDoc on disk, which is then edited and published to the website. Then that gets read, converted to Markdown, and is used to update the release on GitHub. We can probably strip off the |
Has a decision been made yet how this should be solved? |
We should strip off that line (we probably don't need |
The description of the GitHub releases under https://github.com/rust-lang/rust-analyzer/releases uses the format
The problem is that GitHub misinterprets this
#<number>
as issue / PR reference, which is quite confusing:It seems escaping the
#
with a\
has no effect (at least not in the preview), so maybe it would be best to simply omit the#
(or add a zero-width space or similar between)?The text was updated successfully, but these errors were encountered: