[chore] Add release:risky-change on PRs touching certain files #12552
+23
−7
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.
Description
This modifies the "Add code owners to a PR" CI workflow, which automatically adds component-related labels to PRs, to also add the "release:risky-change" label if the PR touches a hard-coded list of files. Currently, this list is:
I also specified the C locale in the
tr
command which gets the PR data. It probably won't matter in the Ubuntu-based CI, but I had issues with the Homebrew core-utils version oftr
when testing locally. I can remove this change if you think it's unnecessary.Link to tracking issue
Fixes #11857
Testing
I did some dry runs locally with a few PRs that did or did not touch the relevant files.