6
0
mirror of https://github.com/ChristianLight/tutor.git synced 2024-12-11 21:57:59 +00:00

Update issue templates

This commit is contained in:
Régis Behmo 2019-05-13 16:40:48 +02:00 committed by Régis Behmo
parent b4e3c43902
commit cac0fb8404
2 changed files with 44 additions and 0 deletions

24
.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View File

@ -0,0 +1,24 @@
---
name: Bug report
about: Report a bug in Tutor
title: ''
labels: ''
assignees: ''
---
**Bug description**
<!-- A clear and concise description of what the bug is. Don't be afraid to include a lot of context and as much background information as possible. If applicable, add screenshots to help explain your problem. -->
<!-- Also include relevant error logs; for instance, to debug the LMS provide the output of `tutor local logs lms --tail=100` -->
<!-- Is this a bug in Tutor, or in Open edX? Open edX bugs should not be reported here, but in the Open edX bug tracker: https://openedx.atlassian.net/ -->
**How to reproduce**
<!-- Include the FULL, EXACT command that you are running and that is causing an error. Also include the FULL, EXACT command output that you see in the console. THIS IS ESPECIALLY IMPORTANT! Thank you :) -->
<!-- In case of a web error, include the URL of the page that is causing the error.-->
<!-- Did you make any manual changes to the generated environment or config.yml files? If yes, describe those changes.-->
**Environment**
<!-- Include your OS (e.g. Mac OS, Ubuntu 18.04...) and the Tutor version that you use, which can be obtained with `tutor --version`. -->
**Additional context**
<!-- Add any other context about the problem here.-->

View File

@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest or encourage the addition of a new feature to Tutor
title: ''
labels: ''
assignees: ''
---
**Is your feature request related to a problem? Please describe.**
<!-- A clear description of what the problem is. Feel free to include as much background information as possible here. It's important that we understand the deeper motivations behind a feature request in order to provide the best possible solution. Ex. "I'm always frustrated when [...]. This is because at my company we do [...]. This is a business requirement because [...]." -->
**Describe the solution you'd like**
<!-- A clear description of what you want to happen -->
**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.-->