Commit f0f148e6 authored by Sébastiaan Versteeg's avatar Sébastiaan Versteeg

Replace GitLab repo templates by GitHub equivalents

parent 52177352
---
name: Bug report
about: Something is not working as expected
title: ''
labels: 'bug, priority: medium'
assignees: ''
---
### Describe the bug
A clear and concise description of what the bug is.
### How to reproduce
Steps to reproduce the behaviour:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
### Expected behaviour
A clear and concise description of what you expected to happen.
### Screenshots
If applicable, add screenshots to help explain your problem.
### Additional context
Add any other context about the problem here.
blank_issues_enabled: false
contact_links:
- name: Our contact information
url: https://thalia.nu/association/committees/42/
about: For any questions not related to this repository
---
name: Feature request
about: You want something new
title: ''
labels: 'feature, priority: low'
assignees: ''
---
### Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
### Describe the solution you'd like
A clear and concise high-level description of what you want to happen.
### Motivation
A clear and concise motivation why we should consider implementing this.
### Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
### Additional context
Add any other context or screenshots about the feature request here.
---
name: Technical change
about: Changes that do not affect the behaviour of the website. If you are not a member of the Technicie, there is a very high chance that you should not use this template
title: ''
labels: 'priority: low, technical change'
assignees: ''
---
### Describe the change
A clear and concise description of what the change should be.
### Motivation
A clear and concise motivation why we should invest in this change.
### Current implementation
If relevant, describe how it's done currently.
### Suggested implementation
Provide (a) suggestion(s) for how we could approach this.
### Additional context
Add any other context or screenshots about the technical change here.
Closes #ISSUE
<!--
Please add the appropriate label for the change that you made to this PR.
That is: feature, bug or technical change.
-->
### Summary
A clear and concise description of the changes that you made. What bug did you solve? Or what feature did you add?
### How to test
Steps to test the changes you made:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
\ No newline at end of file
/label ~bug ~"priority: medium"
### One-sentence description
<!-- What breaks -->
### Current behaviour / Reproducing the bug
<!-- Please write what is happening and how we could reproduce it, if relevant -->
<!--
1. Step 1
2. Step 2
3. ???
4. Breakage
-->
### Expected behaviour
<!-- Please write how what happened did not meet your expectations -->
/label ~feature ~"priority: low"
<!--
You want something new.
-->
### One-sentence description
<!-- What do you want? -->
### Motivation
<!-- Why should we care? -->
### Desired functionality
<!--
What we should support.
Please provide this in general terms, if possible.
You can provide suggestions on how to implement this later.
We like high-level descriptions as those allow us to better consider
the desired result. Assumptions on how the site works don't
necessarily match how we implemented certain things.
-->
### Suggested implementation
<!--
If you have any notes on how we could achieve this feature,
share them here.
-->
/label ~"technical change" ~"priority: low"
<!--
This template is for changes that do not affect the behaviour of the website.
** If you are not in the Technicie, there is a very high chance that you
should not use this template
Examples:
* Changes in CI
* Refactoring of code
* Technicie-facing documentation
-->
### One-sentence description
<!-- Please provide a brief description of the issue. Don't go into specifics. -->
### Why?
<!-- Please motivate why we should invest into this change -->
### Current implementation
<!-- If relevant, describe how it's done currently -->
### Suggested implementation
<!-- Provide (a) suggestion(s) for how we could approach this -->
/label ~feature
Closes #ISSUE
### Short description
### Steps to use this feature
1.
/label ~"technical change"
Closes #ISSUE
### Short description
/label ~bug
Closes #ISSUE
#### Previous behaviour
Steps to reproduce:
1.
#### New behaviour
Steps to validate that it works:
1.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment