Skip to content

Commit 2b76928

Browse files
Add to scenario template
1 parent 3d32d68 commit 2b76928

File tree

1 file changed

+6
-26
lines changed

1 file changed

+6
-26
lines changed
Lines changed: 6 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms
22

33
name: "Sample Scenario"
4-
description: "Suggest a new feature or improvement."
5-
title: "[Feature]: <title>"
4+
description: "Suggest a new API Management Sample Scenario."
5+
title: "[Scenario]: <title>"
66
labels: ["triage"]
77
type: "Feature"
88
assignees:
@@ -11,35 +11,15 @@ body:
1111
- type: markdown
1212
attributes:
1313
value: |
14-
## Feature Request
14+
## Scenario Request
1515
1616
Please fill out the form below to help us understand your request.
1717
1818
- type: textarea
1919
id: feature
2020
attributes:
21-
label: "Describe the feature"
22-
description: "What feature are you proposing?"
23-
placeholder: "Please describe the feature you are proposing."
24-
validations:
25-
required: true
26-
27-
- type: textarea
28-
id: improvement
29-
attributes:
30-
label: "Improvement to Project"
31-
description: "How will it improve this project?"
32-
placeholder: "Please describe how this feature will improve the project."
33-
validations:
34-
required: true
35-
36-
- type: dropdown
37-
id: collaborate
38-
attributes:
39-
label: "Are you able to collaborate and/or submit a pull request?"
40-
description: "Select one."
41-
options:
42-
- "Yes"
43-
- "No"
21+
label: "Describe the scenario"
22+
description: "What scenario are you proposing?"
23+
placeholder: "Please describe the sample scenario / use case you are proposing. What should it demonstrate?"
4424
validations:
4525
required: true

0 commit comments

Comments
 (0)