baalajimaestro/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Update issue templates

Browse source
This commit is contained in:
Ludovic Fernandez 2018-05-07 12:14:02 +02:00 committed by Traefiker Bot
parent 8e64bc8785
commit 97295f270b
3 changed files with 194 additions and 177 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
.github/ISSUE_TEMPLATE/bugs.md → .github/ISSUE_TEMPLATE/Bug_report.md vendored
View file

@ -1,8 +1,14 @@
---
name: Bug report
about: Create a report to help us improve
---
<!-- <!--
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
The issue tracker is for reporting bugs and feature requests only. The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following: For end-user related support questions, please refer to one of the following:
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik - Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://traefik.herokuapp.com - the Traefik community Slack channel: https://traefik.herokuapp.com
@ -18,12 +24,12 @@ Bug
<!-- <!--
HOW TO WRITE A GOOD ISSUE? HOW TO WRITE A GOOD BUG REPORT?
- Respect the issue template as much as possible. - Respect the issue template as much as possible.
- If it's possible use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I. - If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title must be short and descriptive. - The title should be short and descriptive.
- Explain the conditions which led you to write this issue: the context. - Explain the conditions which led you to report this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing. - The context should lead to something, an idea or a problem that you’re facing.
- Remain clear and concise. - Remain clear and concise.
- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown - Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown

14
.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/Custom.md vendored
View file

@ -1,8 +1,14 @@
---
name: Generic issue template
about: For issue or bug
---
<!-- <!--
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
The issue tracker is for reporting bugs and feature requests only. The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following: For end-user related support questions, please refer to one of the following:
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik - Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://traefik.herokuapp.com - the Traefik community Slack channel: https://traefik.herokuapp.com
@ -23,9 +29,9 @@ If you intend to ask a support question: DO NOT FILE AN ISSUE.
HOW TO WRITE A GOOD ISSUE? HOW TO WRITE A GOOD ISSUE?
- Respect the issue template as much as possible. - Respect the issue template as much as possible.
- If it's possible use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I. - If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title must be short and descriptive. - The title should be short and descriptive.
- Explain the conditions which led you to write this issue: the context. - Explain the conditions which led you to report this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing. - The context should lead to something, an idea or a problem that you’re facing.
- Remain clear and concise. - Remain clear and concise.
- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown - Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown

15
.github/ISSUE_TEMPLATE/features.md → .github/ISSUE_TEMPLATE/Feature_request.md vendored
View file

@ -1,8 +1,14 @@
---
name: Feature request
about: Suggest an idea for this project
---
<!-- <!--
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
The issue tracker is for reporting bugs and feature requests only. The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following: For end-user related support questions, please refer to one of the following:
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik - Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://traefik.herokuapp.com - the Traefik community Slack channel: https://traefik.herokuapp.com
@ -21,12 +27,11 @@ Feature
HOW TO WRITE A GOOD ISSUE? HOW TO WRITE A GOOD ISSUE?
- Respect the issue template as much as possible. - Respect the issue template as much as possible.
- If it's possible use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I. - If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title must be short and descriptive. - The title should be short and descriptive.
- Explain the conditions which led you to write this issue: the context. - Explain the conditions which led you to report this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing. - The context should lead to something, an idea or a problem that you’re facing.
- Remain clear and concise. - Remain clear and concise.
- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown - Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown
--> -->