5dd02c462a
chore: add aurorascharff to devex team labeler config ( #90866 )
...
### What?
Add `aurorascharff` to the devex team labeler configuration.
### Why?
New team member onboarding.
### How?
Added username to the relevant pattern entries in the labeler config.
---------
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
2026-03-04 19:19:26 +01:00
a4c1a0cd72
Turbopack: Rename crates/napi to crates/next-napi-bindings and update crate name ( #89314 )
...
Disclaimer: This PR is entirely claude+opencode generated.
- Crate name said `next-swc-napi`, which was confusing, because this has a lot more than swc bindings nowdays.
- The crate name didn't match the directory name, which often confused agents.
This does not change the npm package name, as that would likely have a much larger blast radius, and could break more things, to a point where it may not be worth it.
2026-01-30 15:36:57 -08:00
5ec2d23633
Update labeler.json ( #88591 )
2026-01-15 16:19:02 +00:00
a44f01b166
Update turbopack team members ( #87231 )
2025-12-16 10:21:16 -08:00
8c52bd604e
Update labeler ( #84623 )
2025-10-07 17:14:39 -07:00
9b4cb03e9a
Update to run rspack tests on release ( #82453 )
...
As discussed we can move these tests to run on canary release instead of
on every PR.
x-ref: [slack
thread](https://vercel.slack.com/archives/C02CDC2ALJH/p1754522330101839?thread_ts=1754493332.436339&cid=C02CDC2ALJH )
2025-08-07 16:15:29 -07:00
2eac9dccd8
chore: update username from 'nebrelbug' to 'bgub' ( #81734 )
...
## Update GitHub username in labeler configuration
I just changed my username from "nebrelbug" to "bgub"
2025-07-16 13:58:34 -07:00
37ab1aac49
update: add nebrelbug to labeler.json ( #81437 )
2025-07-09 02:04:49 +00:00
890c11996a
Update workflows for nextjs-bot ( #81134 )
...
This updates to use the new bot account specific for Next.js which we've
already been using for stale issues for a bit.
2025-07-01 10:23:05 -07:00
4620946770
chore: add self to labelers ( #80924 )
2025-06-26 17:57:33 +02:00
47eda30f1a
chore: Update DevEx team changes in labeler ( #79191 )
...
Reflect updates to the DevEx team
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-05-14 08:41:02 +00:00
3719be2c03
fix(CI): Remove comments from labeler config ( #79015 )
...
The labeler reads this as json5 here:
https://github.com/vercel/next-labeler-webhook/blob/1ecc3b54c2b03fae950c7cb2dd859cf63c3e8684/src/app/api/label/utils/fetchConfig.ts#L1
But apparently something else is also reading it and expecting JSON?
2025-05-09 16:48:39 -07:00
c1ea312257
chore(CI): Add Rspack labeler config ( #79004 )
...
This should automatically add the `Rspack` label in most cases, which should let us run the rspack CI in theses cases.
There's an issue with the current CI config where the build-and-test job isn't triggered by label changes, so I'll need to make some changes there, but this is a start.
2025-05-09 16:10:21 -07:00
9bb904d10a
chore(CI): Add a few more turbopack paths to labeler config ( #78980 )
...
Looks like we never added this after the turbopack repo migration.
2025-05-09 16:01:45 -07:00
6f8dd7c44f
chore(CI): Add lukesandberg to turbopack team ( #78074 )
...
Verified over slack that this is the correct username.
2025-04-11 16:57:53 -07:00
1562c9ba48
Add Josh to Turbopack team for created-by label ( #77738 )
...
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
2025-04-02 16:36:25 +00:00
d6dcf36541
Update labeler.json ( #76828 )
...
Reflect team changes.
2025-03-05 17:54:13 +01:00
394ee67a40
misc: add Rauno to CI approved ( #75269 )
2025-01-24 20:06:46 +09:00
5210d119c6
Update labeler config ( #72047 )
...
Removes temporary user from config
2024-10-29 15:24:28 -07:00
0f43e4ea38
Add Jude to nextjs team ( #71936 )
...
### What?
Add @gaojude to Next.js team user group
---------
Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com >
2024-10-27 17:45:30 +00:00
1e493fc8e7
Create React sync automatically ( #69314 )
...
Closes NDX-245
2024-08-28 17:33:57 +02:00
0dfcdea234
Label React syncs in GitHub with type: react-sync ( #67710 )
2024-07-22 20:02:20 +02:00
cad3a51049
refactor: move rust crates to the repo root directory ( #67780 )
...
### Why?
In preparation for moving all turbopack crates
Also makes them easier to work with in general.
Closes PACK-3164
2024-07-22 18:41:27 +02:00
9990516b11
Add LichuAchu and mischnic to labeler ( #67635 )
2024-07-10 10:09:32 -07:00
ba97c7595f
Update labeler.json ( #67359 )
...
### What?
Reflect team changes in labeler list.
2024-07-02 00:00:49 +02:00
710b0b7cd4
chore(github): update users ( #66877 )
...
## Why?
Update the labeler list.
2024-06-14 11:20:29 -07:00
9085ea4b83
Update labeler config for CI approved ( #66335 )
2024-05-29 17:37:36 +02:00
2966b85bcc
add arlyon to turbopack team ( #66177 )
2024-05-24 14:10:30 +00:00
6a9a392059
chore: update labels in workflows/templates ( #63713 )
2024-04-17 14:28:51 +02:00
2670e1c034
Add Ben's handle to labeler ( #64312 )
...
Closes PACK-2932
2024-04-11 08:20:58 +02:00
76b0a1192e
add Sebastian (eps1lon) to "created-by: next.js team" in labeler config ( #63669 )
...
Closes NEXT-2914
2024-03-25 14:39:22 +01:00
c21b8f5a3d
add Janka (@lubieowoce) to "created-by: Next.js team" in labeler config ( #63618 )
2024-03-22 20:09:40 +01:00
6217e3fb10
chore: fix core team members ( #60900 )
...
### What?
Removing an outdated entry, and fixing the casing of another so Workflow
runs are auto-approved.
### Why?
https://github.com/vercel/next.js/pull/60574 fails the CI Workflow Run,
because of a mismatch in GitHub actor and the actual username set in
`labeler.json`
[Ref](https://github.com/vercel/nextjs-hive-docker/blob/c26bc3f26520b41986a0f9467fdc2529f705d81f/validate-job.js#L39-L42 ),
[Slack
thread](https://vercel.slack.com/archives/C03S9JCH2Q5/p1705684536884389?thread_ts=1705436555.494229&cid=C03S9JCH2Q5 )
Closes NEXT-2172
2024-01-19 10:19:32 -08:00
8a3881fef0
Update labeler.json ( #60843 )
...
Add @Ethan-Arrowood to labeler list
2024-01-18 12:15:15 -08:00
be1b9738c8
chore: add myself to created-by: Next.js team ( #60144 )
...
Quick :pr: so the `created-by: Next.js
team` label automatically gets added to my :pr:s.
2024-01-02 14:52:22 -08:00
a6a8c8422c
Update turbopack label creation ( #58214 )
2023-11-08 18:33:44 +00:00
a6844e1eae
cleanup PR labeler config ( #57827 )
...
Removes some usernames that our PR labeler webhook shouldn't apply to
2023-10-31 18:17:45 +00:00
fc86c4123b
Update labeler config ( #52844 )
2023-07-18 18:12:26 +00:00
f6ff2ef98e
[Next Docs] Update Git Workflow ( #50579 )
...
Update our git workflow in preparation for open-sourcing the content of
the docs ([linear
task](https://linear.app/vercel/issue/DX-1579/set-up-github-workflow )).
**Templates:**
- [x] Update docs issue template to encourage contributions
- [x] Update PR template to include link to new contribution guide
**Code Owners / Reviewers:**
- https://github.com/vercel/next.js/pull/50841
**Labels:**
- [x] Add DevEx team to labeler.json so PRs get the "created by: DevEx
team"
**Other:**
- [x] Remove docs manifest from CI checks as we no longer have one (keep
the manifest for errors as they live under `/pages`)
- [x] Add `unifiedjs.vscode-mdx` to the vscode extension list
2023-06-08 12:01:55 +02:00
ecf59365ac
add auto labeling for edge team ( #50842 )
2023-06-06 14:34:41 +00:00
9b2afe509b
add auto labeling for turbopack/the web-tooling team ( #47502 )
2023-03-24 16:30:51 +00:00
6a6977cb71
chore: tweak PR labeler pattern ( #47395 )
...
Co-authored-by: Jan Kaifer <jan@kaifer.cz >
2023-03-22 14:39:24 +01:00
f1fba5b456
chore: improve PR labeling, fix, sort, add new team member ( #46675 )
...
## What?
This PR has its main goal to improve the experience of opening/reviewing
a PR.
It improves the PR template, as well as extends PR auto-labeling.
## Why?
There are 2 parts to the PR template:
- Individual contributors: The current template accommodates for the
most common cases individual contributors use to contribute. (I.e.
fixing bugs, updating/adding examples, addressing documentation issues).
The new template keeps this at the top.
- Next.js team: As maintainers, we should try to explain PRs as if
someone with less context would review them. This should also help with
backreferencing PRs in issues and follow-up PRs and make it easier to
follow changes, understand trade-offs better at the time, and help new
team members catch up over time, etc.
## How?
The template is written in a comment instead of Markdown, so when the PR
is opened, most of the template is hidden to make it less verbose.
The checkboxes we've had before are not shown, but we already auto-label
PRs based on the path of the files that have been touched, so the
checkboxes showed redundant information.
[Slack
thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1677677802109289 ),
Closes NEXT-741
2023-03-07 10:54:46 +01:00
8049ad3048
Update labeler.json with current next.js team members ( #44231 )
...
I added everyone from
https://github.com/orgs/vercel/teams/next-js-engineering/members
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2022-12-21 18:12:20 +01:00
73d7f9458f
Updated Maedahs name in label gen config ( #32005 )
2021-12-01 10:20:11 -06:00
1442b582f5
Add Rich, Maedah, and Ismael to the docs label
2021-12-01 13:18:13 +01:00
f8d6441e41
Add next-swc to labeler
2021-12-01 12:00:30 +01:00
143d32746c
Update labeler.json
2021-11-19 09:19:40 +01:00
cfe608403e
Update labeler.json
2021-11-18 15:12:02 +01:00
70c08e01e1
Update labeler.json
2021-10-18 10:20:53 +02:00
Aurora Scharff
