Skip to content

Commit b290281

Browse files
authored
Update and rename feature_request.md to feature_request.yaml
Signed-off-by: Glenn ten Cate <[email protected]>
1 parent 658b187 commit b290281

File tree

2 files changed

+60
-20
lines changed

2 files changed

+60
-20
lines changed

.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 0 additions & 20 deletions
This file was deleted.
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
name: ✨ Feature Request
2+
description: Suggest a new feature or improvement to the Global Cybersecurity Skills Framework.
3+
title: "[Feature Request]: "
4+
labels: [enhancement, feature-request]
5+
assignees: []
6+
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thank you for taking the time to suggest a new feature!
12+
Please complete the form below so we can understand and evaluate your proposal.
13+
14+
- type: input
15+
id: feature-title
16+
attributes:
17+
label: Feature Title
18+
description: Short title of the feature or enhancement
19+
placeholder: e.g., Add export-to-MarkDown functionality for filtered job roles
20+
validations:
21+
required: true
22+
23+
- type: textarea
24+
id: feature-description
25+
attributes:
26+
label: Feature Description
27+
description: A clear and concise description of the feature you’d like to see.
28+
placeholder: Explain the feature idea, who it benefits, and what problem it solves.
29+
validations:
30+
required: true
31+
32+
- type: textarea
33+
id: motivation
34+
attributes:
35+
label: Why is this feature important?
36+
description: Describe the use case or scenario where this feature would be valuable.
37+
placeholder: e.g., Educators want to export specific job roles with associated skills to create learning pathways.
38+
39+
- type: textarea
40+
id: proposed-solution
41+
attributes:
42+
label: Proposed Solution (optional)
43+
description: If you have an idea on how to implement it, describe it here.
44+
placeholder: e.g., Add a download button in the web UI using existing filtered dataset
45+
46+
- type: checkboxes
47+
id: alternatives
48+
attributes:
49+
label: Have you considered any alternatives?
50+
options:
51+
- label: I’ve considered other approaches and this seems like the best option.
52+
- label: I’m open to other suggestions or implementations.
53+
54+
- type: checkboxes
55+
id: consent
56+
attributes:
57+
label: Contributor Agreement
58+
options:
59+
- label: I agree to follow the Linux Foundation Code of Conduct.
60+
required: true

0 commit comments

Comments
 (0)