archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/.github/CODEOWNERS

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

45 lines
3.1 KiB
Text
Raw Normal View History

Add codeowners file (#6672)
2019-03-15 13:46:01 +01:00
# Learn how to add code owners here:
# https://help.github.com/en/articles/about-code-owners
Update codeowners to be more specific (#30908) * Update codeowners Co-authored-by: Jiachi Liu <inbox@huozhi.im>
2021-11-03 23:34:33 +01:00
Update CODEOWNERS (#54738)
2023-08-29 21:34:33 +02:00
* @timneutkens @ijjk @shuding @huozhi @feedthejim @ztanner @wyattjoh
Make sure DevEx can approve docs PRs / Remove Spaces (#51996)
2023-06-29 19:10:53 +02:00
/.git* @vercel/next-js @vercel/devex
/docs/ @vercel/next-js @vercel/devex
/errors/ @vercel/next-js @vercel/devex
/examples/ @vercel/next-js @vercel/devex
Update codeowners (#51935) revert to the previous version of codeowners before vercel spaces is applied
2023-06-28 21:17:41 +02:00
/scripts/ @vercel/next-js
/.alex* @vercel/next-js @leerob
/.eslint* @vercel/next-js @leerob
/.prettier* @vercel/next-js @leerob
Make sure DevEx can approve docs PRs / Remove Spaces (#51996)
2023-06-29 19:10:53 +02:00
/*.md @vercel/next-js @vercel/devex
/*.mdx @vercel/next-js @vercel/devex
Update codeowners (#51935) revert to the previous version of codeowners before vercel spaces is applied
2023-06-28 21:17:41 +02:00
/packages/create-next-app/ @vercel/next-js
Update teamname in codeowners (#57775) @vercel/web-tooling -> @vercel/turbopack
2023-10-31 13:33:13 +01:00
/pnpm-lock.yaml @vercel/next-js @vercel/turbopack
Move the Next.js team back to github codeowners (#51657) Bring back the previous setting so specific team members get tagged on all PRs.
2023-06-22 19:24:09 +02:00
chore: add new codeowners for cli refactor (#62749) - https://github.com/vercel/next.js/pull/61877#discussion_r1509561939 Closes NEXT-2666
2024-03-02 00:13:19 +01:00
# Next.js CLI
/packages/next/src/bin @timneutkens @ijjk @shuding @samcx
/packages/next/src/cli @timneutkens @ijjk @shuding @samcx
Update codeowners to be more specific (#30908) * Update codeowners Co-authored-by: Jiachi Liu <inbox@huozhi.im>
2021-11-03 23:34:33 +01:00
# Image Component (@styfle)
Update codeowners (#55355) Adds myself to additional codeowner scopes
2023-09-14 15:42:24 +02:00
/**/*image* @timneutkens @ijjk @shuding @styfle @huozhi @ztanner @vercel/devex
/**/*image*/** @timneutkens @ijjk @shuding @styfle @huozhi @ztanner @vercel/devex
/**/*img* @timneutkens @ijjk @shuding @styfle @huozhi @ztanner @vercel/devex
Update codeowners (#51935) revert to the previous version of codeowners before vercel spaces is applied
2023-06-28 21:17:41 +02:00
/packages/next/client/use-intersection.tsx @timneutkens @ijjk @shuding @styfle
Update codeowners (#55355) Adds myself to additional codeowner scopes
2023-09-14 15:42:24 +02:00
/packages/next/server/serve-static.ts @timneutkens @ijjk @shuding @styfle @huozhi @ztanner
/packages/next/server/config.ts @timneutkens @ijjk @shuding @styfle @huozhi @ztanner
Update codeowners (#51250) Tweak code owners after some testing and feedback. - Move the Next.js team up to be optional global code owners (so that everyone can review but are not tagged for review). Global individuals should still be tagged if there are no specific `.vercel.approvers` files in subdirectories. - Adds @vercel/devex to image files so there's coverage on those files for the docs - Target specific folder and files for Styfle to get notified - Deletes some rules in the old GitHub codeowners
2023-06-13 19:47:12 +02:00
Update codeowners (#51935) revert to the previous version of codeowners before vercel spaces is applied
2023-06-28 21:17:41 +02:00
# Tooling & Telemetry
Update teamname in codeowners (#57775) @vercel/web-tooling -> @vercel/turbopack
2023-10-31 13:33:13 +01:00
/packages/next/src/build/ @timneutkens @ijjk @shuding @huozhi @ztanner @feedthejim @vercel/turbopack
/packages/next/src/server/lib/router-utils/setup-dev-bundler.ts @timneutkens @ijjk @shuding @huozhi @feedthejim @ztanner @wyattjoh @vercel/turbopack
Dev Service (#56442) This replaces the `(global as any)._nextDevHandlers` invocation with references to a specific service instance while also removing the module scoped `devInstances`. This ensures that correct types are used. This was done while changing the `match` parameter in `ensurePage` to `definition` which didn't cause a typescript error (it should have).
2023-10-05 19:45:00 +02:00
/packages/next/src/telemetry/ @timneutkens @ijjk @shuding @padmaia
Update teamname in codeowners (#57775) @vercel/web-tooling -> @vercel/turbopack
2023-10-31 13:33:13 +01:00
/packages/next-swc/ @timneutkens @ijjk @shuding @huozhi @vercel/turbopack
Cargo.toml @timneutkens @ijjk @shuding @huozhi @vercel/turbopack
Cargo.lock @timneutkens @ijjk @shuding @huozhi @vercel/turbopack
/.cargo/config.toml @timneutkens @ijjk @shuding @huozhi @vercel/turbopack
/.config/nextest.toml @timneutkens @ijjk @shuding @huozhi @vercel/turbopack
Rename turbopack-tests-manifest to turbopack-dev-tests-manifest (#63409) ## What? - Renames the Turbopack tests manifest to reflect that it only holds development tests. - Creates initial plumbing for Turbopack build tests manifest (currently empty) - Added running tests in the Turbopack builds test manifest on PRs - Implements uploading the Turbopack builds manifest to areweturboyet What this doesn't implement: - Updating the Turbopack builds manifest Open questions: - Since the manifest is empty there are no test results, I had to add handling for that in `run-tests.js`: https://github.com/vercel/next.js/pull/63409/files#diff-269567847b110d8ecaaade3ab592df207bba02c7b446db23d72f18ff0e61d335R359 but not sure if that exit case was added for a specific special reason. <!-- 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 # --> Closes NEXT-2837
2024-03-19 10:26:14 +01:00
/test/build-turbopack-dev-tests-manifest.js @timneutkens @ijjk @shuding @huozhi @vercel/turbopack
/test/turbopack-dev-tests-manifest.json @timneutkens @ijjk @shuding @huozhi @vercel/turbopack
Reference in a new issue Copy permalink