Skip to content

Commit 26637ea

Browse files
CMCDragonkaiCMCDragonkai
committed
Adding gitlab templates
1 parent 3920dc0 commit 26637ea

File tree

6 files changed

+153
-0
lines changed

6 files changed

+153
-0
lines changed

‎.gitlab/issue_templates/bug_report.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
### Describe the bug
11+
<!-- A clear and concise description of what the bug is. -->
12+
13+
### To Reproduce
14+
<!-- Steps to reproduce the behavior (use a code example if possible): -->
15+
1. ...
16+
2. ...
17+
3. ...
18+
19+
### Expected behavior
20+
<!-- A clear and concise description of what you expected to happen. -->
21+
22+
### Screenshots
23+
<!-- If applicable, add screenshots to help explain your problem. -->
24+
25+
### Platform (please complete the following information)
26+
- Device: [e.g. iPhone6]
27+
- OS: [e.g. iOS]
28+
- Version [e.g. 22]
29+
30+
### Additional context
31+
<!-- Add any other context about the problem here. -->
32+
33+
### Notify maintainers
34+
<!--
35+
Check `git blame` for whoever last touched something.
36+
-->

‎.gitlab/issue_templates/design.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
name: Design
3+
about: Design a new feature or architecture (this is usually an epic)
4+
title: ''
5+
labels: design, enhancement
6+
assignees: ''
7+
8+
---
9+
10+
### Requirements of this design
11+
<!-- What are the goals/requirements that this is designed to solve? Examples include "user wants to do X because of Y reason". -->
12+
1. ...
13+
2. ...
14+
3. ...
15+
16+
### Additional context
17+
<!-- Add any other context about the design here. Include prior-work and previous issues. -->
18+
19+
### Specification
20+
<!-- Provide a specification that can be implemented. Add diagrams when possible including hand-drawn drawings. Add screenshots or visual designs (from Figma). -->
21+
1. ...
22+
2. ...
23+
3. ...
24+
25+
### Sub-Issues & Sub-PRs created
26+
<!-- List design/development subissues and PRs derived from this design: -->
27+
1. ...
28+
2. ...
29+
3. ...

‎.gitlab/issue_templates/development.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Development
3+
about: Develop a new feature or architecture, this should be a unit issue
4+
title: ''
5+
labels: development
6+
assignees: ''
7+
8+
---
9+
10+
### Specification
11+
<!-- The specification specifies some behaviour. You can link an existing design issue. -->
12+
13+
### Additional context
14+
<!-- Add any other context about the design here. Include prior-work and previous issues. -->
15+
16+
### Tasks
17+
<!-- Provide a list of implementation tasks that will be needed by the PR implementer. -->
18+
1. ...
19+
2. ...
20+
3. ...

‎.gitlab/issue_templates/feature_request.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
### Is your feature request related to a problem? Please describe.
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+
<!-- A clear and concise description of what you want to happen. -->
15+
16+
### Describe alternatives you've considered
17+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
18+
19+
### Additional context
20+
<!-- Add any other context or screenshots about the feature request here. -->

‎.gitlab/issue_templates/research.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
name: Research
3+
about: Research a new idea
4+
title: ''
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
### What is your research hypothesis/question?
11+
<!-- What is the topic of research here? What is the question attempting to be answered? What are the resources that you intend to read/explore? -->
12+
13+
### Review existing ideas, literature and prior work
14+
<!-- Items of literature, websites, prior work, issues to review and read: -->
15+
1. [ ] ...
16+
2. [ ] ...
17+
3. [ ] ...
18+
19+
### Research conclusion
20+
<!-- Write a conclusion regarding the research after using the comments to indicate progress. This is done at the end. -->
21+
22+
### Sub-Issues & Sub-PRs created
23+
<!-- List design/development subissues and PRs derived from this research: -->
24+
1. ...
25+
2. ...
26+
3. ...

‎.gitlab/merge_request_templates/development.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
### Description
2+
<!-- Write your description about what this PR is about. -->
3+
4+
### Issues Fixed
5+
<!-- List all issues fixed by this PR. -->
6+
* Fixes #...
7+
8+
### Tasks
9+
<!-- List all tasks to be done by this PR. -->
10+
1. [ ] ...
11+
2. [ ] ...
12+
3. [ ] ...
13+
14+
### Final checklist
15+
<!-- Please check what applies. Note that these are not hard requirements but merely serve as information for reviewers. -->
16+
17+
* [ ] Domain specific tests
18+
* [ ] Full tests
19+
* [ ] Updated inline-comment documentation
20+
* [ ] Lint fixed
21+
* [ ] Squash and rebased
22+
* [ ] Sanity check the final build

0 commit comments

Comments
 (0)