Commit d4ae5a17 authored by Jens Reidel's avatar Jens Reidel

Merge branch 'next' into 'next'

update gitlab templates

See merge request !669
parents c61dea33 95f64b7e
Pipeline #2070 failed with stages
in 0 seconds
**Describe the bug**
A clear and concise description of what the bug is.
<!-- Lines like this one will not be visible -->
## Checks
---
<!-- Please only continue if all checkboxes are filled like so: [x] -->
* [ ] I have checked, whether someone else has already reported this bug
* [ ] I can consistently reproduce this bug
## Description
---
<!-- Under this line, describe in detail what happens and how this is a bug.
From this description, we should know the affected commands and possibly which part of the code houses the bug (if you already know what causes it). -->
Example: Using this command causes me to have a negative amount of crates
## To Reproduce
---
<!-- Under this line, include details on how the bug can be replicated.
You can enter as many or as few steps as required. -->
1. Use the command [...]
2. Have another player do [...]
3. Use the reaction [...]
4. While [...] is happening, do [...]
5. etc.
## Device info (if this bug occurs outside of Discord)
---
<!-- If this bug happens outside of the Discord client, i.e. on the raid or guild adventure signup website, fill these details. -->
### Desktop (please fill in the following information)
<!-- Fill in this information when you used a PC. Leave as is if a smartphone was used. -->
- OS: [e.g. iOS, Windows, Linux (which distribution)]
- Browser: [e.g. Chrome, Safari]
- Version: [e.g. 22]
### Smartphone (please fill the following information)
<!-- Fill in this information if you used a smartphone. This includes other smart devices as well. Leave as is if a PC was used. -->
**To Reproduce**
Steps to reproduce the behavior:
1. Do '....'
2. Enter command '....'
3. Hit reaction '....'
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
## Expected behavior
---
<!-- Under this line, enter what the expected behaviour is, what would be "normal" when following the steps. -->
Example: using this command should not give me negative amounts of crates
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
## Screenshots
---
<!-- Under this line, you can add screenshots in the format ![image](image link), for example ![image](https://i.imgur.com/1998lxb.png).
If you don't have any screenshots, simply leave this field blank.
These screenshots should be used to help you explain the issue. -->
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
## Additional context
---
<!-- Under this line, include anything else you'd like us to know, for instance how we can contact you on Discord.
If you have nothing else to add, simply leave this field blank. -->
**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 [...]
<!-- Lines like this one will not be visible -->
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
## Checks
---
<!-- Please only continue if all checkboxes are filled like so: [x] -->
* [ ] I have checked, whether someone else has already suggested this feature
* [ ] This is a feature that is beneficial to the greater commmunity
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
## Is your feature request related to a problem? Please describe.
---
<!-- Under this line, write a clear and concise description of what the problem is. -->
Example: I am unhappy with the amount of item types
**Additional context**
Add any other context or screenshots about the feature request here.
## Describe the solution you'd like
---
<!-- Under this line, outline how you would like this problem to be solved. -->
Example: I would like to see more item types in the bot, perhaps Axes or Bows
## Describe alternatives you've considered
---
<!-- Under this line, describe any other ways you have considered of solving the problem.
If you have not considered another way to solve the issue, simply leave this field blank, however having alternatives is preferred. -->
## Additional context
---
<!-- Under this line, include anything else you'd like us to know, for instance how we can contact you on Discord.
If you have nothing else to add, simply leave this field blank. -->
- **Please check if the PR fulfills these requirements**
<!-- Lines like this one will not be visible -->
* [ ] The commit message follows our guidelines
## Please check if the PR fulfills these requirements
---
<!-- Please only continue if all checkboxes are filled like so: [x]
The second and third checkboxes are only necessary if this PR changes code, rather than text only. -->
* [ ] The commit message follows our [guidelines](../../CONTRIBUTING.md)
* [ ] Tests for the changes have been added (for bug fixes / features)
* [ ] Docs have been added / updated (for bug fixes / features)
- **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
* **What is the current behavior?** (You can also link to an open issue here)
## What kind of change does this PR introduce?
---
<!-- Bug fix, feature, docs update, correcting text, QoL, etc. -->
- **What is the new behavior (if this is a feature change)?**
* **Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?)
## What is the current behavior?
<!-- How the bot behaves before this PR. You can also link to an open issue here. -->
- **Other information**:
## What is the new behavior (if this is a feature change)?
---
<!-- If this PR implements a new feature or changes an existing one, describe how the bot will behave after the PR is accepted. -->
## Does this PR introduce a breaking change?
---
<!-- What changes might users need to make in their application due to this PR? Breaking changes include, but are not limited to: database scheme updates, usage of new config variables, new command modules, etc. -->
## Additional context
---
<!-- Under this line, include anything else you'd like us to know, for instance how we can contact you on Discord.
If you have nothing else to add, simply leave this field blank. -->
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