-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
We have two change logs #2777
Comments
Yep the default behaviour is to write to docs/changelog.md and it simply prepends to the existing file. The path is specified in the merge yml link
Needs to change to:
I'll try and find time for a PR soon, but if not, that is all that needs to change. |
@JAForbes I would love to do this (easy) task. |
Sure! It is probably a bit more involved than just moving the content of
If you want to try and generate one, you can have a look at https://github.com/compose-regexp/compose-regexp.js/blob/main/scripts/build-toc.js which should work with few modifications. The script currently replaces the TOC in the middle of the page, but it should instead move it back at the top after const tocMatcher = sequence(lookBehind('<!-- START toc -->\n'), /[^]*?/, lookAhead('<!-- END toc -->')) should become const tocMatcher = /<!-- START toc -->[^]*?<!-- END toc -->/ You can add the corresponding tags around the TOC at the start of the file, and tweak (note that I'm fine not having a TOC there) |
In changelog.md is the date of release mentioned as well. In recent-changes.md this information missing. Would it be possible to add the date of the release automatically? |
We currently have
From now on, it would seem reasonable to rely on the automated logs. If pr-release is flexible enough, we could tell it to update
changelog.md
. If it isn't we can move the old entries torecent-changes.md
and special-case that file in the build-docs script to put its content in https://mithril.js.org/changelog.html.Edit, actually, https://mithril.js.org/recent-changes.html is live, but not linked to from anywere.
The text was updated successfully, but these errors were encountered: