-
Notifications
You must be signed in to change notification settings - Fork 14
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
feature request: list releases with second level headings #14
Comments
GitHub provides Markdown ToC in web UI. Personally it's sufficient for me. What is your use case? https://github.blog/changelog/2021-04-13-table-of-contents-support-in-markdown-files/
This feature looks easy for me. Once I understand reasonable use case, I would be able to implement it soon. |
My use case is that I am using Sphinx to build a static html website for the documentation of a Python package. Without this feature the whole list of H1 headings would end up as being elements of the main table of contents of the website. Whereas being H2, they are not. I have seen that you have already implemented it. Thanks 🚀 |
I see. That looks nice use case to me. I'll consider to add an option to generate ToC. |
At b0badff, I added cat <<-EOS > test.md
CHANGELOG
=========
## Releases
EOS
changelog-from-release -l 2 -t >> test.md generate the following output: https://gist.github.com/rhysd/186a723397431906d9491ab196143d04 Does it look good to you? I wonder date of release should be included in list item like |
I may misunderstand your use case. Is the ToC list generated by Sphinx (so it is not necessary to be done by changelog-from-release)? |
Yes, the ToC is defined within Sphinx, so I just needed the possibility to choose the heading level. With the last changes at #b0badff it will be possible to set the main title. Great, thanks! |
OK, thank you for the clarification. I'll revert the commit and close this issue. |
It would be amazing if there was a feature (possibly called with a command line argument) that would list releases as second level headings, possibly prepended by something like a "# Changelog" first level heading.
It would be useful when including the .md file in an index, without having all single releases showing up in the toctree.
I would contribute myself, but unfortunately i know very little of Go. Do you think this is worth implementing? Thanks 🚀
The text was updated successfully, but these errors were encountered: