chore: add issue labeler #43599
Merged
chore: add issue labeler #43599
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
balazsorban44
commented
Dec 1, 2022
| - 'Turbopack (--turbo)' | ||
| 'area: TypeScript': | ||
| - 'TypeScript' | ||
| # Less used/old/redundant labels |
There was a problem hiding this comment.
Some of these have 0 items currently, are superseded by other labels, or are irrelevant for auto-labeling. We can delete some of these labels, and move legit issues under the new label (eg.: Server Components -> app dir)
Failing test suitesCommit: 6cacd5a
Expand output● basePath › should navigate to /404 correctly client-side ● basePath › should navigate to /_error correctly client-side ● basePath › should navigate to external site and back ● basePath › should handle query/hash correctly during query updating #hello? $search ● basePath › should handle query/hash correctly during query updating #? $search ● basePath › should handle query/hash correctly during query updating ## $search ● basePath › should handle query/hash correctly during query updating ##? $search ● basePath › should handle query/hash correctly during query updating ##hello? $search ● basePath › should handle query/hash correctly during query updating ##hello $search ● basePath › should handle query/hash correctly during query updating #hello?world $search ● basePath › should handle query/hash correctly during query updating #a ?hello=world ● basePath › should handle query/hash correctly during query updating #a ?hello ● basePath › should handle query/hash correctly during query updating #a ?hello= ● basePath › should navigate back correctly to a dynamic route ● basePath › should not update URL for a 404 ● basePath › should handle 404 urls that start with basePath ● basePath › should update dynamic params after mount correctly ● basePath › should navigate to index page with getStaticProps ● basePath › should work with nested folder with same name as basePath ● basePath › should work with normal dynamic page ● basePath › should work with hash links ● basePath › should work with catch-all page ● basePath › should navigate an absolute url ● basePath › should navigate an absolute local url with basePath ● basePath › should navigate an absolute local url without basePath ● basePath › should 404 when manually adding basePath with ● basePath › should 404 when manually adding basePath with router.push ● basePath › should 404 when manually adding basePath with router.replace ● basePath › should show the hello page under the /docs prefix ● basePath › should have correct router paths on first load of / ● basePath › should have correct router paths on first load of /hello ● basePath › should fetch data for getStaticProps without reloading ● basePath › should fetch data for getServerSideProps without reloading ● basePath › should have correct href for a link ● basePath › should have correct href for a link to / ● basePath › should show the other-page page under the /docs prefix ● basePath › should navigate to the page without refresh ● basePath › should use urls with basepath in router events ● basePath › should use urls with basepath in router events for hash changes ● basePath › should use urls with basepath in router events for cancelled routes ● basePath › should use urls with basepath in router events for failed route change ● basePath › should allow URL query strings without refresh ● basePath › should allow URL query strings on index without refresh ● basePath › should correctly replace state when same asPath but different url Read more about building and testing Next.js in contributing.md. |
balazsorban44
requested review from
timneutkens,
ijjk,
shuding,
styfle,
huozhi and
padmaia
as code owners
balazsorban44
commented
Dec 1, 2022
| @@ -45,7 +46,6 @@ body: | |||
| - 'SWC transpilation' | |||
| - 'Turbopack (--turbo)' | |||
| - 'TypeScript' | |||
| - 'Other' | |||
There was a problem hiding this comment.
The dropdown is optional, besides there is a default "None" added by GitHub, so this is not necessary.
There was a problem hiding this comment.
Weird. I wouldn't expect that GitHub adds none when its multiple: true.
balazsorban44
force-pushed
the
chore/auto-label-issues
branch
from
99648d3
to
b3fbf61
Compare
|
LGTM |
jankaifer
approved these changes
Dec 1, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Follow-up of #43228. This PR adds a new GitHub Action that matches the issue's body for the dropdown list items and adds the relevant labels to the issue for triaging automatically.
Bug
fixes #numbercontributing.mdFeature
fixes #numbercontributing.mdDocumentation / Examples
pnpm build && pnpm lint