diff options
| author | bors <bors@rust-lang.org> | 2023-05-31 15:24:03 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-05-31 15:24:03 +0000 |
| commit | 594a2cba93d8c78f522bdb15de6aeebeebf50a8a (patch) | |
| tree | d01dba6fd4664004ceaba00d3f37e5909c3b1183 | |
| parent | e85869578dfb64a0edda602bb26982e80ec579e8 (diff) | |
| parent | de62139513b486ae4cdf1ca68c6eae5daca25cc8 (diff) | |
| download | rust-594a2cba93d8c78f522bdb15de6aeebeebf50a8a.tar.gz rust-594a2cba93d8c78f522bdb15de6aeebeebf50a8a.zip | |
Auto merge of #10852 - Alexendoo:issue-template, r=flip1995
Remove lint name and category fields from the new lint issue form changelog: none Picking a name/category is something the implementers/reviewers tend to cover anyway, I think asking people to come up with it at the time of their suggestion is more of a barrier than it's worth Inspired by the mention in #10849
| -rw-r--r-- | .github/ISSUE_TEMPLATE/new_lint.yml | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/.github/ISSUE_TEMPLATE/new_lint.yml b/.github/ISSUE_TEMPLATE/new_lint.yml index 0b43d8d70c0..b49493edce1 100644 --- a/.github/ISSUE_TEMPLATE/new_lint.yml +++ b/.github/ISSUE_TEMPLATE/new_lint.yml @@ -12,29 +12,6 @@ body: description: What does this lint do? validations: required: true - - type: input - id: lint-name - attributes: - label: Lint Name - description: Please provide the lint name. - - type: dropdown - id: category - attributes: - label: Category - description: > - What category should this lint go into? If you're unsure you can select - multiple categories. You can find a category description in the - `README`. - multiple: true - options: - - correctness - - suspicious - - style - - complexity - - perf - - pedantic - - restriction - - cargo - type: textarea id: advantage attributes: |