Here's the PR: #4860

If/when this is merged, someone with admin access to this (backdrop-issues) repo will need to enable the wiki, and create an initial 'Home' page (apparently at least one wiki page must exist for the action to work).

Thanks for working on this @BWPanda 🙏

Awesome, thanks @BWPanda! I'm not sure we need the wiki page component of it. IMO it will be sufficient for us to be able to download the asset ZIP from the build job (assuming that happens). Let's give a shot with the 1.18.0 milestone and see how it goes.

I've merged the PR, though I'm leaving this open because I think we'll likely need further adjustments.

Wow, it works! I closed the 1.18.0 milestone and it made this nice wiki page!

https://github.com/backdrop/backdrop-issues/wiki/1.18.0

Picture for posterity in the event we remove this page:

I really like how it can automatically map our labels to particular categories like "Bug fixes" vs "Features". Apparently it can also generate a list of "contributors" based on the people involved in the issues! Very neat.

I'm not sure this is the best use of the Wiki however. We could take a few options from here:

• We could embrace use of the Wiki and move our "procedures" into it: https://github.com/backdrop/backdrop-issues/tree/master/procedures We would also probably group all release notes into a directory.
• We could remove the saving of the notes to the wiki, and instead save the markdown file as a job artifact using https://docs.github.com/en/free-pro-team@latest/actions/guides/storing-workflow-data-as-artifacts Then we could download the artifact from the build job (this example being https://github.com/backdrop/backdrop-issues/runs/1654183699?check_suite_focus=true)

For the time being, I'm leaning towards the second approach. Even if we start using the GitHub wiki more extensively, I am not sure that putting the release notes in it is really helpful for our users. We may end up with people starting to link to both the release note Wiki pages and the Release pages (onto which we copy release notes). I think we'd prefer to just have them in one place.

@quicksketch Glad it worked! 🎉

I like the idea of moving the procedural docs to the wiki, but I'll leave that for a separate issue. And I agree that having release notes in two places isn't ideal, so I've gone ahead and changed the action to upload the notes as an artifact instead. I closed (and re-opened the milestone) and here's the result: https://github.com/backdrop/backdrop-issues/actions/runs/465228286

That link allows you to download a zip file that has the release node markdown file in it.

So if you're happy with this solution, you can:

• Delete the release notes from the wiki (but leave the wiki in place for now as I'll open an issue about moving the docs there)
• Remove dragonbot's token from the repo settings (not needed anymore)

Super! I'll delete that token since I feel it's good to be tidy about such things. This is a great solution and will save us hours of work every single release. Thanks so much @BWPanda!