]>
Commit | Line | Data |
---|---|---|
0a29b90c FG |
1 | name: Feature Request |
2 | description: Suggest an idea for enhancing Cargo | |
49aad941 | 3 | labels: ["C-feature-request", "S-triage"] |
0a29b90c FG |
4 | body: |
5 | - type: markdown | |
6 | attributes: | |
7 | value: | | |
8 | Thanks for filing a 🙋 feature request 😄! | |
9 | ||
10 | If the feature request is relatively small and already with a possible solution, this might be the place for you. | |
11 | ||
12 | If you are brewing a big feature that needs feedback from the community, [the internal forum] is the best fit, especially for pre-RFC. You can also talk the idea over with other developers in [#t-cargo Zulip stream]. | |
13 | ||
14 | [the internal forum]: https://internals.rust-lang.org/c/tools-and-infrastructure/cargo/15 | |
15 | [#t-cargo Zulip stream]: https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo | |
16 | - type: textarea | |
17 | id: problem | |
18 | attributes: | |
19 | label: Problem | |
20 | description: > | |
21 | Please provide a clear description of your use case and the problem | |
22 | this feature request is trying to solve. | |
23 | validations: | |
24 | required: true | |
25 | - type: textarea | |
26 | id: solution | |
27 | attributes: | |
28 | label: Proposed Solution | |
29 | description: > | |
30 | Please provide a clear and concise description of what you want to happen. | |
31 | - type: textarea | |
32 | id: notes | |
33 | attributes: | |
34 | label: Notes | |
35 | description: Provide any additional context or information that might be helpful. |