-
Notifications
You must be signed in to change notification settings - Fork 43
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
Create a GitHub Actions to draft the release announcements #351
Comments
From a matrix chat: @oraNod and I were chatting earlier about the possibility of using github actions to help create a clean release announcement (and maybe auto-post it to the news/newsletter category in the forum). It seems something that's ripe for automation and could simplify the release manager's task (especially as the announcement is the last thing on a long list of tasks). And also the other bits and bobs - correct link to pypi, the SHA and zip file locations etc etc. Basically take human error out of it all and let automation create it. From there, with some discourse API magic, it could be autoposted (much like the meeting logs are autoposted today). |
I would suggest a script to generate this based on a Jinja2 template. It could interact with the Discourse API and/or sendmail to auto-post. We could also potentially integrate into the release playbook. |
I guess I could just assign this one to myself and send a PR... |
@samccann Hey I've been hacking around with this a bit this evening. Still have some things to work out with posting to discourse but I pushed a couple changes to my fork that you can try out. It at least demonstrates what I had in mind about passing inputs to the action then generating an announcement from a standard template. https://github.com/oraNod/ansible-build-data/actions/workflows/announce_major_release.yml |
Hey looks good! I don't have the 'run workflow' option but I can see what the workflow is doing. I think the other input has to be the core version for sure. But maybe the better approach is to get #258 merged and then figure out what other inputs there might be. |
Thanks. Getting #258 merged first seems like a good way to go. We can follow that up with the inputs and workflow to generate templates. |
Yes, can we please merge #258. |
@anweshadas could you address the review comments in #258? |
Inspired by @oraNod's work, I started working on an antsibull-build subcommand to generate these announcements based on jinja2 templates in ansible-community/antsibull#573. I would like to add functionality to open pre-filled mailto: and forum entry links with the generated announcement text as well. |
It should be possible to use https://docs.python.org/3/library/webbrowser.html#webbrowser.open for this. FYI. |
Since we've had some typos etc in recent release announcements for the Ansible package, the idea surfaced to create a GitHub Actions that would take the template announcements being created in #258 and fill in the correct details.
The text was updated successfully, but these errors were encountered: