fork/cargo

git clone https://git.julia.blue/fork/cargo

borsAuto merge of #9970 - ehuss:issue-template-forms, r=alexcrichtonad85ec9fc

0.89.0
2.1 KiB50 linesraw
1name: Tracking Issue
2description: A tracking issue for an accepted feature or RFC in Cargo.
3title: "Tracking Issue for _FEATURE_NAME_"
4labels: ["C-tracking-issue"]
5body:
6  - type: markdown
7    attributes:
8      value: >
9        Thank you for creating a tracking issue! Tracking issues are for tracking an
10        accepted feature or RFC from implementation to stabilization. Please do not
11        file a tracking issue until the feature or RFC has been approved.
12  - type: textarea
13    id: summary
14    attributes:
15      label: Summary
16      description: Please provide a very brief summary of the feature.
17      value: |
18        RFC: [#NNNN](https://github.com/rust-lang/rfcs/pull/NNNN) <!-- If this is an RFC -->
19        Original issue: #NNNN <!-- if there is a related issue that spawned this feature -->
20        Implementation: #NNNN <!-- link to the PR that implemented this feature if applicable -->
21        Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#my-feature
22
23        Please enter a short, one-sentence description here.
24    validations:
25      required: true
26  - type: textarea
27    id: unresolved
28    attributes:
29      label: Unresolved Issues
30      description: List issues that have not yet been resolved.
31      placeholder: |
32        * [ ] Make a list of any known implementation or design issues.
33  - type: textarea
34    id: future
35    attributes:
36      label: Future Extensions
37      description: >
38        An optional section where you can mention where the feature may be
39        extended in the future, but is explicitly not intended to
40        address.
41  - type: textarea
42    id: about
43    attributes:
44      label: About tracking issues
45      description: Please include this notice in the issue.
46      value: |
47        Tracking issues are used to record the overall progress of implementation.
48        They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
49        A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
50        Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.