-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Publish GitHub release notes? #2933
Comments
Hi @jab, thanks for the suggestion. I wouldn't mind at all using GitHub Releases, only that right now we have an automated system using |
@nicoddemus (cc @blueyed @asottile) - I've been putting something together for Hypothesis to run Sphinx with the plain Feel free to copy it! I had a quick look at If you have something that can run after release in CI (or even just as a manual script) though, updating both GH releases and Tidelift is basically painless. |
(Nice to know Hypothesis is also on Tidelift! 😁) Thanks for sharing this. I've had a brief conversation with @jaraco in jaraco/jaraco.tidelift#1, which has started I believe the hardest part of a general "upload release notes" process is getting the release notes, as projects use wildly different approaches to that. Anyway the work you already done is definitely great already, and can be used as basis for a more general project, or something that works with This thread also gives me the idea of writing a generic "changelog uploader to Tidelift and GH release notes", based on towncrier (at least initially). Ahh so many interesting projects to tackle, so little time. 😁 |
Just to note, Tidelift now automatically scans for GitHub release notes, so just uploading the release notes to GH will also solve this for Tidelift. 👍 |
Any interest in publishing release notes to https://github.com/pytest-dev/pytest/releases?
This would help users follow progress more proactively, especially if using tools such as Sibbell. Currently pages like https://sibbell.com/github/pytest-dev/pytest/3.2.5/ are blank because of the lack of release notes.
The text was updated successfully, but these errors were encountered: