Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor contributing guide #39778

Closed

Conversation

timneutkens
Copy link
Member

Splits contributing guide into a directory with multiple files that are linked from the main contributing.md file.

  • Added additional details on linting.
  • Added explanation of stable vs canary channel and how to publish them for maintainers.
  • Added explanation on how a version is decided.
  • Changed recommendation for fork workflow to use GitHub CLI instead.
  • Changed testing recommendation to always be headless + narrow down the run. Changed command to pnpm test to simplify.
  • Added "why" and "the fix" for pnpm new-error, also added logging of the error url at the end of the command.

Bug

  • Related issues linked using fixes #number
  • Integration tests added
  • Errors have 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 helpful link attached, see contributing.md

Documentation / Examples

  • Make sure the linting passes by running pnpm lint
  • The examples guidelines are followed from our contributing doc

@timneutkens timneutkens marked this pull request as draft August 20, 2022 12:59
@balazsorban44
Copy link
Member

Closing in favor of #40515. All comments will be addressed there. Will mark it as ready for review when it is ready. 🙏

balazsorban44 added a commit that referenced this pull request Sep 13, 2022
balazsorban44 added a commit that referenced this pull request Sep 13, 2022
ijjk added a commit that referenced this pull request Sep 16, 2022
Continues #39778

Closes #40499

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have 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 helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm lint`
- [ ] The examples guidelines are followed from [our contributing
doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)

Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
Co-authored-by: JJ Kasper <jj@jjsweb.site>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
created-by: Next.js team PRs by the Next.js team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants