Use the new GitHub issues template (#13168)
Co-authored-by: Huáng Jùnliàng <jlhwung@gmail.com>
This commit is contained in:
Nicolò Ribaudo
GitHub
parent
0cfe3dc107
commit
e92d6b2458
61
.github/ISSUE_TEMPLATE/Bug_report.md
vendored
61
.github/ISSUE_TEMPLATE/Bug_report.md
vendored
@ -1,61 +0,0 @@
|
||||
---
|
||||
name: "\U0001F41B Bug Report"
|
||||
about: "If something isn't working as expected \U0001F914."
|
||||
title: ''
|
||||
labels: 'i: bug, i: needs triage'
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Bug Report
|
||||
|
||||
<!-- If you would like to implement a PR, we are more than happy to help you go through the process!-->
|
||||
- [ ] I would like to work on a fix!
|
||||
|
||||
<!--
|
||||
@babel/eslint-parser:
|
||||
If you are having issues with JSX you might want to check out eslint-plugin-react. If there's an issue with new experimental syntax you might need to check if it's supported by @babel/eslint-plugin.
|
||||
-->
|
||||
|
||||
**Current behavior**
|
||||
<!-- A clear and concise description of the behavior. -->
|
||||
|
||||
- [REPL](https://babel.dev/repl), [Codesandbox](https://codesandbox.io/s/babel-repl-custom-plugin-7s08o?file=/src/index.js), or GitHub Repo may increase triaging priority!
|
||||
|
||||
**Input Code**
|
||||
|
||||
```js
|
||||
var your => (code) => here;
|
||||
```
|
||||
|
||||
**Expected behavior**
|
||||
<!-- A clear and concise description of what you expected to happen (or code). -->
|
||||
|
||||
**Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)**
|
||||
<!--- Tip: You can also run Babel with the environment variable SHOW_CONFIG_FOR=your_file_path to print all configs associated with a path-->
|
||||
<!-- https://babeljs.io/docs/en/configuration#print-effective-configs for more information -->
|
||||
|
||||
- Filename: `babel.config.js`
|
||||
|
||||
```js
|
||||
{
|
||||
"your": { "config": "here" }
|
||||
}
|
||||
```
|
||||
|
||||
**Environment**
|
||||
<!--- Tip: Instead of filling out the questions below, you can run `npx envinfo --preset babel` and paste the result below ``` -->
|
||||
```
|
||||
|
||||
```
|
||||
- Babel version(s): [e.g. v7.12.0]
|
||||
- Node/npm version: [e.g. Node 12/npm 7]
|
||||
- OS: [e.g. macOS 10.15.4, Windows 10]
|
||||
- Monorepo: [e.g. yes/no/Lerna]
|
||||
- How you are using Babel: [e.g. `webpack`, `rollup`, `parcel`, `babel-register`]
|
||||
|
||||
**Possible Solution**
|
||||
<!--- If you have suggestions on a fix for the bug -->
|
||||
|
||||
**Additional context**
|
||||
<!-- Add any other context about the problem here. Or a screenshot if applicable -->
|
||||
23
.github/ISSUE_TEMPLATE/Feature_request.md
vendored
23
.github/ISSUE_TEMPLATE/Feature_request.md
vendored
@ -1,23 +0,0 @@
|
||||
---
|
||||
name: "\U0001F680 Feature Request"
|
||||
about: "I have a specific suggestion for Babel!"
|
||||
title: ''
|
||||
labels: 'i: enhancement, i: needs triage'
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Feature Request
|
||||
|
||||
<!-- Check this if you would like to implement a PR, we are more than happy to help you go through the process !-->
|
||||
- [ ] I would like to work on this feature!
|
||||
|
||||
**Is your feature request related to a problem?**
|
||||
<!-- A concise description of what the problem is. Ex. I have an issue when [...] -->
|
||||
|
||||
**Describe the solution you'd like**
|
||||
|
||||
**Describe alternatives you've considered**.
|
||||
|
||||
**Documentation, Adoption, Migration Strategy**
|
||||
<!-- If you can, explain how users will be able to use this and how it might be documented. Maybe a mock-up? -->
|
||||
108
.github/ISSUE_TEMPLATE/bug_report.yml
vendored
Normal file
108
.github/ISSUE_TEMPLATE/bug_report.yml
vendored
Normal file
@ -0,0 +1,108 @@
|
||||
name: "🐛 Bug Report"
|
||||
description: "If something isn't working as expected 🤔."
|
||||
title: "[Bug]: "
|
||||
labels: ["i: needs triage"]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: Thanks for taking the time to file a bug report! Please fill out this form as completely as possible.
|
||||
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: ""
|
||||
options:
|
||||
- label: Would you like to work on a fix?
|
||||
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: How are you using Babel?
|
||||
options:
|
||||
- babel-loader (webpack)
|
||||
- "@rollup/plugin-babel"
|
||||
- "@babel/eslint-parser"
|
||||
- "@babel/cli"
|
||||
- "@babel/register or @babel/node"
|
||||
- Programmatic API (`babel.transform`, `babel.parse`)
|
||||
- Other (Next.js, Gatsby, vue-cli, ...)
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Input code
|
||||
description: |
|
||||
You must write here the minimal input code necessary to reproduce the bug.
|
||||
Even better, you can share a link to the Babel [REPL](https://babel.dev/repl):
|
||||
this will make it easier for us to reproduce the issue, and it may help fixing
|
||||
the bug sooner.
|
||||
If it's not possible to reproduce the bug with a single file, a GitHub Repository
|
||||
is also ok.
|
||||
placeholder: |
|
||||
```js
|
||||
var your => (code) => here;
|
||||
```
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: Configuration file name
|
||||
description: |
|
||||
**NOTE**: If it's possible that Babel is not correctly loading your config, it's probably because you are using
|
||||
`.babelrc`/`package.json` instead of `babel.config.json`.
|
||||
multiple: true
|
||||
options:
|
||||
- babel.config.json
|
||||
- babel.config.js
|
||||
- babel.config.cjs
|
||||
- babel.config.mjs
|
||||
- .babelrc.json
|
||||
- .babelrc.js
|
||||
- .babelrc.cjs
|
||||
- .babelrc.mjs
|
||||
- .babelrc
|
||||
- package.json
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Configuration
|
||||
description: |
|
||||
**Tip:** You can also run Babel with the environment variable SHOW_CONFIG_FOR=your_file_path to print all configs associated with a path.
|
||||
See https://babeljs.io/docs/en/configuration#print-effective-configs for more information
|
||||
placeholder: |
|
||||
```json
|
||||
{
|
||||
"your": { "config": "here" }
|
||||
}
|
||||
```
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Current and expected behavior
|
||||
description: A clear and concise description of what Babel is doing and what you would expect.
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Environment
|
||||
description: |
|
||||
**Tip:** you can run `npx envinfo --preset babel` and paste the result below
|
||||
placeholder: |
|
||||
- Babel version(s): [e.g. v7.12.0]
|
||||
- Node: [e.g. Node 15]
|
||||
- npm/Yarn version: [e.g. npm 7/Yarn 2.3]
|
||||
- OS: [e.g. macOS 10.15.4, Windows 10]
|
||||
- Monorepo: [e.g. yes/no/Lerna]
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Possible solution
|
||||
description: "If you have suggestions on a fix for the bug."
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Additional context
|
||||
description: "Add any other context about the problem here. Or a screenshot if applicable."
|
||||
44
.github/ISSUE_TEMPLATE/feature_request.yml
vendored
Normal file
44
.github/ISSUE_TEMPLATE/feature_request.yml
vendored
Normal file
@ -0,0 +1,44 @@
|
||||
name: "🚀 Feature Request"
|
||||
description: "I have a specific suggestion for Babel!"
|
||||
title: ""
|
||||
labels: ["i: needs triage", "i: enhancement"]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: Thanks for taking the time to suggest a new feature! Please fill out this form as completely as possible.
|
||||
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: ""
|
||||
description: |
|
||||
Check this if you would like to implement a PR, we are more than happy to help you go through the process
|
||||
options:
|
||||
- label: Would you like to work on this feature?
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: What problem are you trying to solve?
|
||||
description: |
|
||||
A concise description of what the problem is.
|
||||
placeholder: |
|
||||
I have an issue when [...]
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Describe the solution you'd like
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Describe alternatives you've considered
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Documentation, Adoption, Migration Strategy
|
||||
description: |
|
||||
If you can, explain how users will be able to use this and how it might be documented. Maybe a mock-up?
|
||||
Loading…
x
Reference in New Issue
Block a user