Skip to content

Commit ca9ac44

Browse files
Gerome-ElassaadGerome-Elassaad
committed
Add GitHub issue templates
1 parent 1b4d938 commit ca9ac44

3 files changed

Lines changed: 74 additions & 0 deletions

File tree

‎.github/ISSUE_TEMPLATE/epic.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: Epic
3+
about: Epics define long-term vision and capabilities of the software. They will never be finished but serve as umbrella for features.
4+
title: ''
5+
labels:
6+
- epic
7+
assignees: ''
8+
---
9+
10+
# Strategic Impact
11+
12+
<!-- Why does this area matter? How is it integrated into the product or the development process? What would happen if we ignore it? -->
13+
14+
# Target Audience
15+
16+
<!-- Who benefits most from improvements in this area?
17+
18+
Usual values: Software Developers using the IDE | Contributors -->
19+
20+
# Capabilities
21+
22+
<!-- which existing capabilities or future features can be imagined that belong to this epic? This list serves as illustration to sketch the boundaries of this epic.
23+
Once features are actually being planned / described in detail, they can be linked here. -->

‎.github/ISSUE_TEMPLATE/feature.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: Feature
3+
about: A pretty vague description of how a capability of our software can be added or improved.
4+
title: ''
5+
labels:
6+
- feature
7+
assignees: ''
8+
---
9+
10+
# Motivation
11+
12+
<!-- What capability should be either established or improved? How is life of the target audience better after it's been done? -->
13+
14+
# Scope
15+
16+
<!-- This is kind-of the definition-of-done for a feature.
17+
Try to keep the scope as small as possible and prefer creating multiple, small features which each solve a single problem / make something better
18+
-->
19+
20+
# Options
21+
22+
<!-- If you already have an idea how this can be implemented, please describe it here.
23+
This allows potential other contributors to join forces and provide meaningful feedback prio to even starting work on it.
24+
-->
25+
26+
# Related
27+
28+
<!-- Link to the epic or other issues or PRs which are related to this feature. -->

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
---
8+
9+
**Is your feature request related to a problem? Please describe:**
10+
11+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
12+
13+
**Describe the solution you'd like:**
14+
15+
<!-- A clear and concise description of what you want to happen. -->
16+
17+
**Describe alternatives you've considered:**
18+
19+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
20+
21+
**Additional context:**
22+
23+
<!-- Add any other context or screenshots about the feature request here. -->

0 commit comments

Comments
 (0)