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.
Use actions/labeler to apply directory labels
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.