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

Restore default issue template.

Browse source
This commit is contained in:
Ludovic Fernandez 2018-05-07 14:16:02 +02:00 committed by Traefiker Bot
parent 97295f270b
commit dce65ab9c2
1 changed files with 73 additions and 79 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1,79 +1,73 @@
--- <!--
name: Generic issue template DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
about: For issue or bug
The issue tracker is for reporting bugs and feature requests only.
--- 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
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. - the Traefik community Slack channel: https://traefik.herokuapp.com
The issue tracker is for reporting bugs and feature requests only. -->
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 ### Do you want to request a *feature* or report a *bug*?
- the Traefik community Slack channel: https://traefik.herokuapp.com
<!--
--> If you intend to ask a support question: DO NOT FILE AN ISSUE.
-->
### Do you want to request a *feature* or report a *bug*? ### What did you do?
<!-- <!--
If you intend to ask a support question: DO NOT FILE AN ISSUE.
--> HOW TO WRITE A GOOD ISSUE?
### What did you do? - 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.
HOW TO WRITE A GOOD ISSUE? - The context should lead to something, an idea or a problem that you’re facing.
- Remain clear and concise.
- Respect the issue template as much as possible. - 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
- 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. ### What did you expect to see?
- 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
For the Traefik Docker image: ex: docker run traefik traefik version
docker run [IMAGE] version -->
ex: docker run traefik version
```
For the alpine Traefik Docker image: (paste your output here)
docker run [IMAGE] traefik version ```
ex: docker run traefik traefik version
--> ### What is your environment & configuration (arguments, toml, provider, platform, ...)?
``` ```toml
(paste your output here) # (paste your configuration 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 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)
```