OilfieldToolsNet/shlink
4
0
Fork 0
mirror of https://github.com/shlinkio/shlink.git synced 2024-11-21 08:34:31 -06:00
Code Issues Packages Projects Releases Wiki Activity

Improve repro steps description in bug issue template

Browse Source
This commit is contained in:
Alejandro Celaya 2024-07-28 10:49:24 +02:00 committed by GitHub
parent 64d7ac7093
commit 6b0b52853c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.github/ISSUE_TEMPLATE/Bug.yml vendored
View File

@ -61,7 +61,11 @@ body:
label: Minimum steps to reproduce label: Minimum steps to reproduce
value: | value: |
<!-- <!--
Emphasis in MINIMUM: What is the simplest way to reproduce the bug? Simple but detailed way to reproduce the bug:
Avoid things like "Create a kubernetes cluster", or anything related with cloud providers, as that is rarely the root cause and the bug may be closed as "not reproducible".
If you can provide a simple docker compose config, that's even better. * Avoid things like "create a kubernetes cluster", or anything related with cloud providers, as that is rarely the root cause.
* Avoid too vague steps or one-liners like "Update from v1 to v2".
* Providing the reproduction in the form of a self-contained docker-composer is desirable.
Failing in any of these will cause the issue to be closed as "not reproducible".
--> -->