-
Notifications
You must be signed in to change notification settings - Fork 28k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add issue labeler #43599
chore: add issue labeler #43599
Conversation
- 'Turbopack (--turbo)' | ||
'area: TypeScript': | ||
- 'TypeScript' | ||
# Less used/old/redundant labels |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
@@ -45,7 +46,6 @@ body: | |||
- 'SWC transpilation' | |||
- 'Turbopack (--turbo)' | |||
- 'TypeScript' | |||
- 'Other' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird. I wouldn't expect that GitHub adds none when its multiple: true
.
99648d3
to
b3fbf61
Compare
LGTM |
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 #number
contributing.md
Feature
fixes #number
contributing.md
Documentation / Examples
pnpm build && pnpm lint