0a2e183476
# Objective This PR begins integrating the new releate-content drafting process (https://github.com/bevyengine/bevy/pull/18427) into our GitHub workflows. It's similar to what we had before: Messages are posted to PRs tagged with `M-Needs-Release-Note` or `M-Needs-Migration-Guide` asking them to add the required material and linking to the instructions. These messages do not trigger if the PR already has modified files in the `release-notes` or `migration-guides` directories (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](https://jekyllrb.com/docs/front-matter/). ## Reviewer Questions + Do we want to add a CI rule actually requiring tagged PRs to create/modify files in the correct directories, or is the message prompt enough? + Do we want to add a CI rule to lint the metadata, for example to enforce that the PR number is included in the files it modifies? |
||
|---|---|---|
| .. | ||
| action-on-PR-labeled.yml | ||
| ci-comment-failures.yml | ||
| ci.yml | ||
| dependencies.yml | ||
| docs.yml | ||
| example-run-report.yml | ||
| example-run.yml | ||
| post-release.yml | ||
| send-screenshots-to-pixeleagle.yml | ||
| validation-jobs.yml | ||
| weekly.yml | ||
| welcome.yml | ||