Use actions/labeler to apply directory labels #9826
Merged
Conversation
This file contains 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
Today the legacy PR processor is used to apply directory labels, but it is the only repository to do so. This uses a common GitHub Action to do the same thing. Another benefit is that the configuration now lives close to the code. A possible downside is that if there are changes, it needs to be cherry picked. That's unlikely, given how little these change. It may even be a benefit when files move around. It gives the possibility to use different labels in different branches.
evgeni
approved these changes
Sep 11, 2023
4 tasks
|
theforeman/prprocessor#181 removes it from prprocessor. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Today the legacy PR processor is used to apply directory labels, but it is the only repository to do so. This uses a common GitHub Action to do the same thing. Another benefit is that the configuration now lives close to the code.
A possible downside is that if there are changes, it needs to be cherry picked. That's unlikely, given how little these change. It may even be a benefit when files move around. It gives the possibility to use different labels in different branches.