-
Notifications
You must be signed in to change notification settings - Fork 373
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's body isn't rendered as Markdown #780
Comments
That's a GitHub issue I think. Someone needs to manually copy those notes, click Edit on the release and paste them again, then it actually becomes markdown. |
I see, I'm going to check if there's a way to tell GitHub that it's markdown. |
Okay I found the cause. So, the problem is we don't pass the notes to GitHub but only include them in the git tag. GitHub will render the passed body as Markdown but if the body is empty, they will instead use git tag's description as plain text. |
Yeah that'd be appropriate! |
See https://github.com/kubernetes-sigs/krew/releases/tag/v0.4.3. https://github.com/kubernetes-sigs/krew/releases/tag/v0.4.2 is rendered correctly, so there should be something between them.
The text was updated successfully, but these errors were encountered: