Commits
User selector
Datepicker
Commit History
Commits on Sep 24, 2024
Commits on Sep 23, 2024
- committed
Sep 23, 2024
Commits on Aug 5, 2024
Commits on Jul 9, 2024
Commits on Jul 8, 2024
Commits on Jul 5, 2024
Commits on Jun 18, 2024
Commits on May 14, 2024
Commits on Apr 22, 2024
Commits on Oct 25, 2023
Commits on Sep 29, 2023
Commits on Sep 28, 2023
Commits on Sep 7, 2023
Commits on Aug 4, 2023
Commits on Jun 8, 2023
Commits on May 12, 2023
### After <img width="304" alt="CleanShot 2023-05-12 at 12 30 06@2x" src=https://github.com/vercel/next.js/commits/canary/"https://github.com/vercel/next.js/assets/6324199/3918dc89-2bc0-4f11-a646-553fe1f0fbf4"> <!-- 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 or adding/fixing 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 # -->" class="color-fg-default" href="https://github.com/vercel/next.js/commit/a0edc92bbcb5b15c11616affb5fe334f2854f46d">Optimize trace span relationships (#49697 ### After <img width="304" alt="CleanShot 2023-05-12 at 12 30 06@2x" src=https://github.com/vercel/next.js/commits/canary/"https://github.com/vercel/next.js/assets/6324199/3918dc89-2bc0-4f11-a646-553fe1f0fbf4"> <!-- 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 or adding/fixing 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 # -->" class="color-fg-default" href="https://github.com/vercel/next.js/commit/a0edc92bbcb5b15c11616affb5fe334f2854f46d">)
Commits on Apr 19, 2023
Commits on Apr 14, 2023
Commits on Apr 3, 2023
Commits on Mar 14, 2023
Commits on Mar 13, 2023
Commits on Feb 13, 2023
![kodiakhq[bot]](https://avatars.githubusercontent.com/in/29196?v=4&size=32){kind=avatar}
Commits on Jan 28, 2023
Commits on Dec 12, 2022
Commits on Dec 5, 2022
Commits on Oct 30, 2022
Commits on Sep 27, 2022
Commits on Sep 16, 2022
- committed
Sep 16, 2022
Commits on Jul 13, 2022
Commits on Jul 7, 2022
- committed
Jul 7, 2022
