16a0e5af32
## What? - Rendering `next info` output as code in the bug template - Removed the "Feature Request" issue template, in favor of a more granular discussion template - Added a minimal template for Help discussions ## Why? The main part of this PR is the new Feature Request template. Anyone can propose a change to Next.js. However adding new features often requires community discussions - whether to align expectations, understand the consequences (eg.: backward compatibility/lifetime of a feature), to look at and understand historical reasons for the current behavior or lack of the feature -, which [GitHub discussions](https://github.com/vercel/next.js/discussions) is more suited for than issues. ## How? - Utilizing the new discussion templates https://docs.github.com/en/discussions/managing-discussions-for-your-community/creating-discussion-category-forms - Adding a link to the [new issue](https://github.com/vercel/next.js/issues/new/choose) view to make it easier to discover [Slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1670874727319809) Closes NEXT-742 ---------
33 lines
849 B
YAML
33 lines
849 B
YAML
body:
|
|
- type: textarea
|
|
attributes:
|
|
label: Goals
|
|
description: Short list of what the feature request aims to address?
|
|
value: |
|
|
1.
|
|
2.
|
|
3.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Non-Goals
|
|
description: Short list of what the feature request _does not_ aim to address?
|
|
value: |
|
|
1.
|
|
2.
|
|
3.
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
attributes:
|
|
label: Background
|
|
description: Discuss prior art, why do you think this feature is needed? Are there current alternatives?
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Proposal
|
|
description: How should this feature be implemented? Are you interested in contributing?
|
|
validations:
|
|
required: true
|