Test thread for release announcements

[EliahKagan]

Warning

This is not an actual announcement thread, just a test of a possible future enhancement.

This discussion is for testing a way to allow release announcements to be posted in such a way that makes it easy to get notified specifically when there is a release of gitoxide, but not other releases. The idea is that if release.yml posts to a discussion thread, then users who only want to be notified of releases produced in release.yml--which are those associated with the gitoxide crate but not other gitoxide crates--could subscribe to that thread.

This experiment relates to GitoxideLabs#1311.

This discussion thread is just for testing. These are not actual release announcements. This is an unofficial exploration of an idea, which is why it's in my fork. This is also why I haven't made this discussion an announcement discussion--it will not be of interest even to most people who doing something with this fork.

However, if this technique is ever used, then:

• A discussion would need to be created on the upstream repository, probably as an announcement discussion.
• The new discussion's title should not beginning with case variant of test, [test, or (test, and with an initial post quite different from this one.
• The new discussion should be locked, so people don't accidentally attempt to start conversations about releases there, which would notify people who only want to be notified of releases. This test discussion is locked to test that the Actions job can still post to it.
• Appropriate GitHub Actions variables would need to be set in the upstream repository. This would consist at least of adding a RELEASE_ANNOUNCEMENTS_URL variable with the URL of the new discussion.
• A pull request with the new announce-release job added would need to be merged. As of this writing, no such pull request yet exists.

Changes to the experimental implementation may affect specifically would have to be done to use it. In addition, other design changes or bugs may result in some of the above information here being inaccurate.

I've temporarily renamed this discussion to not start like [[(]?test\b, to test that this causes the experimental job properly refuses to post about a test release (such as one where the version ends with -DO-NOT-USE) to it.

[github-actions[bot]]

gitoxide v0.39.0-alpha.1-DO-NOT-USE has been released.

[github-actions[bot]]

gitoxide v0.39.0-alpha.2-DO-NOT-USE has been released.