chore: fix issue labeler (#47206)
### What? A fork of https://github.com/github/issue-labeler that we pull in and maintain. ### Why? The official issue labeler had some issues which I tried to fix in PRs and eventually got merged upstream, but the release cycle was a bit slow, and that GitHub action had many parts we did not really need anyway. So it makes sense to maintain it ourselves. ### How? This PR removes the https://github.com/vercel/next.js/blob/canary/.github/issue-labeler.yml config file, which in our case is just a sublist of https://github.com/vercel/next.js/labels anyway. Instead, we can pull in the labels from GitHub directly and filter out those that we want to apply to issues. This will keep things more in sync. fix NEXT-750 ([link](https://linear.app/vercel/issue/NEXT-750)) ---------
Showing
This source diff could not be displayed because it is too large.
You can
view the blob
instead.
This diff is collapsed.
Please
register
or
sign in
to comment