Move release-content content to _release-content#23638
Move release-content content to _release-content#23638dylansechet wants to merge 1 commit intobevyengine:mainfrom
release-content content to _release-content#23638Conversation
|
Surely we should merge this so |
|
I agree with @Zeophlite here @mockersf. We can just do this again if more slip through. |
I prefer to block tooling that can be easily worked around, than features or bug fixes 🙂
Merging a PR isn't "free", it costs a lot in various CI... and I prefer not to merge PRs that will maybe need to be redone later and are not blocking now. Also, keeping the issue / this PR opened and in the milestone is a very good reminder to recheck when creating the release that everything is in the correct folder |
|
@mockersf I'm disregarding any potential costs with this but, would bulk-removing then re-adding the migration guide label help for those PRs? I just added the label to one of them and the GitHub bot correctly reported that the migration guide was missing (because it was under the old |
|
Yeah, resetting the migration guide label is fine, but it's probably easier and clearer just to copy-paste a comment to these authors telling them to update their PRs :) |
A couple PRs got merged in still using
release-contentinstead of_release-content. Fixes #23631.