-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
fix including of CHANGELOG.rst #151
Conversation
Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
The |
Also, I saw the release notes 1.6.0 here on GitHub contain lots of old PR like #23 and many others. Should this be fixed? |
Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
Hi @ssbarnea! I have a few questions:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can fix release draft by updating PR titles and labels, even for merged changes. Still, if a release was already made the release notes are no longer updated and if you want to patch them, you need to manually edit the release.
It can take up to a minute for release drafter to refresh the drafter after you make a change.
And yes, feel free to remove the less interesting changes from changelog as its purpose is to inform users of the library not contributors. Contributors can always check git log. :D
Docs label does not have any special meaning, you need to also add either |
for building documentation. Building the documentation will fail when broken links are found. Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
….gitignore Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
- fix broken links in README.rst - fix broken links in CHANGELOG.rst - cleanup release 1.6.0 to only include actual changes from that release Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
Hi @ssbarnea! I fixed a lot of old links (mostly 302 redirects and broken links). Please also have a look at my proposed release 1.6.0 changelog entry. If you approve, I will edit the 1.6.0 release notes here on GitHub accordingly. For the older releases, I did not change the content, just the presentation and markup. You can find the newly rendered read the docs here: https://ansi2html--151.org.readthedocs.build/changelog.html There is now also a sphinx linkcheck build step while building the documentation. It breaks the build if it finds broken links. One more question: The This is ready to review. |
@ssbarnea Am I allowed to edit the Release Notes here (https://github.com/pycontribs/ansi2html/releases/tag/1.6.0) and make them the same as what is now in |
Sure! |
Done. |
Currently building the documentation does not include the changelog. It fails with the following error:
As can be seen here the changelog in the documentation is empty. The documentation built by this CI run does include the recent changelog.