baalajimaestro/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 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

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

@ -1,72 +1,78 @@
<!-- ---
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. name: Bug report
about: Create a report to help us improve
The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following: ---
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik <!--
- the Traefik community Slack channel: https://traefik.herokuapp.com DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
--> The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, please refer to one of the following:
### Do you want to request a *feature* or report a *bug*? - Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://traefik.herokuapp.com
Bug
-->
### What did you do?
<!-- ### Do you want to request a *feature* or report a *bug*?
HOW TO WRITE A GOOD ISSUE? Bug
- Respect the issue template as much as possible. ### What did you do?
- If it's possible use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title must be short and descriptive. <!--
- Explain the conditions which led you to write this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing. HOW TO WRITE A GOOD BUG REPORT?
- 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 - Respect the issue template as much as possible.
- If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
--> - The title should be short and descriptive.
- Explain the conditions which led you to report this issue: the context.
### What did you expect to see? - The context should lead to something, an idea or a problem that you’re facing.
- 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
### What did you see instead? -->
### What did you expect to see?
### Output of `traefik version`: (_What version of Traefik are you using?_)
<!-- ### What did you see instead?
For the Traefik Docker image:
docker run [IMAGE] version
ex: docker run traefik version
### Output of `traefik version`: (_What version of Traefik are you using?_)
For the alpine Traefik Docker image:
docker run [IMAGE] traefik version <!--
ex: docker run traefik traefik version For the Traefik Docker image:
--> docker run [IMAGE] version
ex: docker run traefik version
```
(paste your output here) For the alpine Traefik Docker image:
``` docker run [IMAGE] traefik version
ex: docker run traefik traefik version
### What is your environment & configuration (arguments, toml, provider, platform, ...)? -->
```toml ```
# (paste your configuration here) (paste your output here)
``` ```
<!-- ### What is your environment & configuration (arguments, toml, provider, platform, ...)?
Add more configuration information here.
--> ```toml
# (paste your configuration here)
```
### If applicable, please paste the log output in DEBUG level (`--logLevel=DEBUG` switch)
<!--
``` Add more configuration information here.
(paste your output here) -->
```
### If applicable, please paste the log output in DEBUG level (`--logLevel=DEBUG` switch)
```
(paste your output here)
```

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

@ -1,73 +1,79 @@
<!-- ---
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. name: Generic issue template
about: For issue or bug
The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following: ---
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik <!--
- the Traefik community Slack channel: https://traefik.herokuapp.com DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
--> The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, please refer to one of the following:
### Do you want to request a *feature* or report a *bug*? - Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://traefik.herokuapp.com
<!--
If you intend to ask a support question: DO NOT FILE AN ISSUE. -->
-->
### What did you do? ### Do you want to request a *feature* or report a *bug*?
<!-- <!--
If you intend to ask a support question: DO NOT FILE AN ISSUE.
HOW TO WRITE A GOOD ISSUE? -->
- Respect the issue template as much as possible. ### What did you do?
- If it's possible use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title must be short and descriptive. <!--
- Explain the conditions which led you to write this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing. HOW TO WRITE A GOOD ISSUE?
- 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 - Respect the issue template as much as possible.
- If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
--> - The title should be short and descriptive.
- Explain the conditions which led you to report this issue: the context.
### What did you expect to see? - The context should lead to something, an idea or a problem that you’re facing.
- 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
### What did you see instead? -->
### What did you expect to see?
### Output of `traefik version`: (_What version of Traefik are you using?_)
<!-- ### What did you see instead?
For the Traefik Docker image:
docker run [IMAGE] version
ex: docker run traefik version
### Output of `traefik version`: (_What version of Traefik are you using?_)
For the alpine Traefik Docker image:
docker run [IMAGE] traefik version <!--
ex: docker run traefik traefik version For the Traefik Docker image:
--> docker run [IMAGE] version
ex: docker run traefik version
```
(paste your output here) For the alpine Traefik Docker image:
``` docker run [IMAGE] traefik version
ex: docker run traefik traefik version
### What is your environment & configuration (arguments, toml, provider, platform, ...)? -->
```toml ```
# (paste your configuration here) (paste your output here)
``` ```
<!--
Add more configuration information here. ### What is your environment & configuration (arguments, toml, provider, platform, ...)?
-->
```toml
# (paste your configuration here)
### If applicable, please paste the log output at DEBUG level (`--logLevel=DEBUG` switch) ```
<!--
``` Add more configuration information here.
(paste your output here) -->
```
### If applicable, please paste the log output at DEBUG level (`--logLevel=DEBUG` switch)
```
(paste your output here)
```

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

@ -1,32 +1,37 @@
<!-- ---
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. name: Feature request
about: Suggest an idea for this project
The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following: ---
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik <!--
- the Traefik community Slack channel: https://traefik.herokuapp.com DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
--> The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, please refer to one of the following:
### Do you want to request a *feature* or report a *bug*? - Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://traefik.herokuapp.com
Feature
-->
### What did you expect to see?
<!-- ### Do you want to request a *feature* or report a *bug*?
HOW TO WRITE A GOOD ISSUE? Feature
- Respect the issue template as much as possible. ### What did you expect to see?
- If it's possible use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title must be short and descriptive. <!--
- Explain the conditions which led you to write this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing. HOW TO WRITE A GOOD ISSUE?
- 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 - Respect the issue template as much as possible.
- If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
--> - The title should be short and descriptive.
- 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.
- 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
-->