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

17 lines
512 B
Text
Raw Normal View History

Adjust Commit Linting Hook (#9694)
2019-12-11 03:29:39 +01:00
**/.next/**
**/_next/**
Pre-ncc compiled packages to prevent re-nccing unnecessarily (#11569) * Pre-ncc compiled packages to prevent re-nccing unnecessarily * Add compiled files * Re-run pre-ncc step * Add check to workflow to ensure pre-compiled doesnt need updating * Update check-pre-compiled script * Add handling for lower case license while nccing * bump Co-authored-by: Joe Haddad <joe.haddad@zeit.co>
2020-04-07 15:42:16 +02:00
**/dist/**
Extract next-swc Rust code into its own package (#31635) Co-authored-by: JJ Kasper <jj@jjsweb.site> Co-authored-by: Tim Neutkens <tim@timneutkens.nl> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2021-11-21 12:59:56 +01:00
packages/next-swc/crates/**
Fix prettierignore_staged for compiled (#44550) Corrects the glob from the `src` folder change. Fixes: https://github.com/vercel/next.js/actions/runs/3833725939/jobs/6525483379
2023-01-04 00:54:11 +01:00
packages/next/src/compiled/**/*
feat: webpack inlining with configuration for v4 / v5 (#20598)
2021-01-14 02:59:08 +01:00
packages/next/bundles/webpack/packages/*.runtime.js
Do not prettify `lerna.json`
2020-05-04 03:56:17 +02:00
lerna.json
Move next-codemod to Next.js monorepo (#15536)
2020-08-10 11:14:53 +02:00
packages/next-codemod/transforms/__testfixtures__/**/*
packages/next-codemod/transforms/__tests__/**/*
hmr error improvements (#30616) Co-authored-by: Hannes Bornö <hannes.borno@vercel.com> Co-authored-by: Hannes Bornö <borno.hannes@gmail.com>
2023-01-06 20:35:16 +01:00
test/development/basic/hmr/components/parse-error.js
Fix typo `pnpm-lock.yam` in `.prettierignore_staged` (#42212) Fix typo `pnpm-lock.yam` in #38915 Regenerate pnpm-lock.yaml without formatting (#42208) <!-- 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 that you're making: --> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) None of the above Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-10-31 06:58:45 +01:00
pnpm-lock.yaml
chore: verify missing/invalid/private reproduction links (#54724) ### What? This PR adds a new action that verifies if the reproduction link is correct _after_ the issue has been created. If it is not, we close the issue and comment on it with the correct steps to take. Check out the [rendered comment here](https://github.com/balazsorban44/next.js/blob/chore/gh-invalid-link-checker/.github/actions/issue-validator/repro-link/invalid-link.md). Additionally, this PR also does some refactoring to simplify our GitHub actions related to issues. Tests: Issue that was supposed to be closed: - https://github.com/balazsorban44/next.js/issues/48 - Issue comment: https://github.com/balazsorban44/next.js/issues/48#issuecomment-1698836121 - Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023209630 - Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023209629 Issue that was not supposed to be closed (closed manually afterward): - https://github.com/balazsorban44/next.js/issues/49 - Issue opened action: https://github.com/balazsorban44/next.js/actions/runs/6023214256 - Issue labeled action: https://github.com/balazsorban44/next.js/actions/runs/6023214258 ### Why? Unfortunately, GitHub is currently missing the [functionality to require a valid reproduction link](https://github.com/orgs/community/discussions/10227) in issue templates. Even if that was supported, this PR adds functionality that could not be covered with a regex validation. Namely, we check if the reproduction is a private repo or not, and potentially could also check the structure to see if it's an actual Next.js project. ### How? If the link is not in the expected section, not a GitHub, CodeSandbox, or Replay.io link, or does not return an OK response (eg.: private repo/sandbox), the issue is closed/commented. Related: - https://github.com/orgs/community/discussions/4629 - https://github.com/orgs/community/discussions/10227 Co-authored-by: Steven <229881+styfle@users.noreply.github.com>
2023-08-30 19:40:57 +02:00
.github/actions/issue-validator/*/index.mjs
Migrate validate links script from next-site and setup GitHub action (#51365) This PR migrates and adapts the [validate docs links script from `next-site`](https://github.com/vercel/front/pull/23185). This script is triggered by a GitHub action whenever a file in the `/docs` folder is updated. If broken links are found in the docs, the check fails and we post a comment on the PR with a list of broken links. Co-authored-by: Michael Novotny <446260+manovotny@users.noreply.github.com>
2023-06-20 15:19:06 +02:00
.github/actions/validate-docs-links/lib/index.js
chore: add GitHub Action to manage "+1" comments (#52866) ### What? Adds a GitHub Action that automatically marks unhelpful comments as "off-topic". You can test it by adding off-topic comments to this issue: https://github.com/balazsorban44/next.js/issues/21 https://github.com/balazsorban44/next.js/blob/17e3ec30689a2323161260c9b03bb7f51ed008f9/.github/actions/minus-one/src/index.mjs#L6 ### Why? A common problem is when an issue thread receives "+1" comments, it usually encourages others to do the same. This makes the thread harder and harder for maintainers to read, without adding value to the discussion. ### How? When an issue receives a comment, we compare it to a list that we determine as off-topic. If it matches, we hide the comment. See: https://docs.github.com/en/graphql/reference/mutations#minimizecomment
2023-07-20 11:34:29 +02:00
.github/actions/needs-triage/index.js
chore: add GH action to notify about pending PRs (#53541) Send us daily notifications when approved and open PRs haven't been merged yet. See [Slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1690610821861229) for more context. It queries: https://github.com/search?q=repo%3Avercel%2Fnext.js%20is%3Apr%20is%3Aopen%20review%3Aapproved%20&type=pullrequests for the number of PRs, then posts a message with a link to https://github.com/vercel/next.js/pulls?q=is%3Apr+is%3Aopen+review%3Aapproved
2023-08-03 23:40:28 +02:00
.github/actions/*/index.mjs
Fix typo `pnpm-lock.yam` in `.prettierignore_staged` (#42212) Fix typo `pnpm-lock.yam` in #38915 Regenerate pnpm-lock.yaml without formatting (#42208) <!-- 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 that you're making: --> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) None of the above Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-10-31 06:58:45 +01:00
**/convex/_generated/**
Reference in a new issue Copy permalink