We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The release notes may look better if instead of formatting it like
* core * change 1 * change 2 * solvers * change 1 * change 2
we instead used Markdown headers, like
#### core * change 1 * change 2 #### solvers * change 1 * change 2
It may also be easier for people to write release notes in this format, al they won't have to deal with nested bullets.
Finally, this would allow linking to the notes for a specific submodule, since every Markdown header gets an anchor.
Level 4 headers may be better level 3. Level 4 renders the same as just bold text, but with an anchor.
The text was updated successfully, but these errors were encountered:
Although as for people writing the notes like this in the PR template, they would probably get confused by the header level, and write notes like
So that may not be a great idea.
Sorry, something went wrong.
No branches or pull requests
The release notes may look better if instead of formatting it like
we instead used Markdown headers, like
core
solvers
It may also be easier for people to write release notes in this format, al they won't have to deal with nested bullets.
Finally, this would allow linking to the notes for a specific submodule, since every Markdown header gets an anchor.
Level 4 headers may be better level 3. Level 4 renders the same as just bold text, but with an anchor.
The text was updated successfully, but these errors were encountered: