Add basic release content tagging workflow#18568
Merged
alice-i-cecile merged 10 commits intobevyengine:mainfrom Mar 27, 2025
Merged
Add basic release content tagging workflow#18568alice-i-cecile merged 10 commits intobevyengine:mainfrom
alice-i-cecile merged 10 commits intobevyengine:mainfrom
Conversation
NthTensor
added
C-Docs
Person-93
reviewed
Mar 27, 2025
alice-i-cecile
added
A-Build-System
doup
reviewed
Mar 27, 2025
Contributor
doup
left a comment
doup
left a comment
There was a problem hiding this comment.
I checked it on your fork and the messages are looking good. Left a couple of suggestions for the templates for common issues when integrating with bevy-website.
doup
reviewed
Mar 27, 2025
BD103
approved these changes
Mar 27, 2025
Member
BD103
left a comment
BD103
left a comment
There was a problem hiding this comment.
I just reviewed the CI, but it looks like it should work!
Contributor
Author
|
Since it's come up a few times, I want to mention that the tool I am writing to merge the notes together will ideally also translate H1 headings into H3 or whatever. This is pretty easy to do, and I've done it before. The rational is that the writers of individual notes really shouldn't have to know about the final structure, and it just makes things a bit more flexible. |
doup
approved these changes
Mar 27, 2025
NthTensor
added
S-Ready-For-Final-Review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objective
This PR begins integrating the new releate-content drafting process (#18427) into our GitHub workflows. It's similar to what we had before: Messages are posted to PRs tagged with
M-Needs-Release-NoteorM-Needs-Migration-Guideasking them to add the required material and linking to the instructions. These messages do not trigger if the PR already has modified files in therelease-notesormigration-guidesdirectories (respectively).I have also re-arranged and content slightly (to remove the need for a directory with the current version number), tweaked the language, and switched the templates to use the standard markdown frontmatter format.
Reviewer Questions