WIP: Automatically generate change logs for each build

[Bejofo]

Summary

Infrastructure "Automatically generate change logs for each build"

Purpose of change

My attempt at #52477
Make creating change logs easier.

Describe the solution

Every time a release is built, a python script fetches all the releases of the past week, and compiles into
a markdown file.

There is already a generate_changelog.py in in the tools, but I don't know how to use it.

[lgtm-com]

This pull request introduces 1 alert when merging 438db55 into 946ed1d - view on LGTM.com

new alerts:

• 1 for Testing equality to None

[Maleclypse]

@Bejofo I notice this is still in draft. Is that intentional?

[Bejofo]

@Maleclypse The current implementation is quite hacky and bare bones. I thought I might work on it some more, but I never got around to it. Should I close this, and reopen when I have a more polished version?

[Maleclypse]

@Maleclypse The current implementation is quite hacky and bare bones. I thought I might work on it some more, but I never got around to it. Should I close this, and reopen when I have a more polished version?

I think it's fine to leave open. If you never come back to it the stale bot will eat it. I wanted to check though.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not 'bump' or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

[stale]

This issue has been automatically closed due to lack of activity. This does not mean that we do not value the issue. Feel free to request that it be re-opened if you are going to actively work on it