archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/.github/workflows
History
Tim Neutkens 81c6b5690b
Add TURBOPACK_DEV to distinguish dev/build in test suite (#63653) 
## What?

Similar to `TURBOPACK_BUILD` this adds `TURBOPACK_DEV`. In a follow-up
PR I'm going to change the `test/integration` suite to check for
`TURBOPACK_DEV` instead of `TURBOPACK`.

<!-- 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-2909
2024-03-25 10:28:35 +01:00
..
build_and_deploy.yml Add tarball deployments for each build (#62969) 2024-03-13 11:39:44 -07:00
build_and_test.yml Add TURBOPACK_DEV to distinguish dev/build in test suite (#63653) 2024-03-25 10:28:35 +01:00
build_reusable.yml chore: upgrade turbo to 1.12.5 (#63163) 2024-03-11 20:35:54 -04:00
cancel.yml chore: update github actions (#61517) 2024-02-01 22:13:29 +01:00
code_freeze.yml chore: upgrade turbo to 1.12.5 (#63163) 2024-03-11 20:35:54 -04:00
issue_lock.yml chore: update github actions (#61517) 2024-02-01 22:13:29 +01:00
issue_popular.yml chore: add pull_request_popular workflow (#61760) 2024-02-07 14:59:46 -08:00
issue_stale.yml chore: fix stale issue closing GH Action (#63523) 2024-03-20 14:38:55 +00:00
notify_release.yml chore: update github actions (#61517) 2024-02-01 22:13:29 +01:00
pull_request_popular.yml chore(github-workflow): update pull_request_popular name (#61967) 2024-02-12 23:11:19 +00:00
pull_request_stats.yml chore: upgrade turbo to 1.12.5 (#63163) 2024-03-11 20:35:54 -04:00
retry_test.yml chore: update github actions (#61517) 2024-02-01 22:13:29 +01:00
setup-nextjs-build.yml chore: update github actions (#61517) 2024-02-01 22:13:29 +01:00
test_e2e_deploy.yml chore: upgrade turbo to 1.12.5 (#63163) 2024-03-11 20:35:54 -04:00
test_examples.yml Revert "Revert actions/setup-node v4 bump" (#61640) 2024-02-04 14:06:28 -08:00
triage.yml chore: auto-close non-labeled issues 2024-02-12 16:14:14 +01:00
trigger_release.yml Fix trigger_release workflow to not publish empty canaries (#63167) 2024-03-12 15:16:19 +00:00
turbopack-nextjs-build-integration-tests.yml Add TURBOPACK_DEV to distinguish dev/build in test suite (#63653) 2024-03-25 10:28:35 +01:00
turbopack-nextjs-dev-integration-tests.yml Add TURBOPACK_DEV to distinguish dev/build in test suite (#63653) 2024-03-25 10:28:35 +01:00
turbopack-update-tests-manifest.yml Implement Turbopack build manifest update (#63461) 2024-03-19 13:00:33 +01:00
turbopack-upload-tests-manifest.yml Split dev and build test run for Turbopack (#63511) 2024-03-20 10:05:16 +01:00
update_fonts_data.yml Revert "Revert actions/setup-node v4 bump" (#61640) 2024-02-04 14:06:28 -08:00