Mirrors/ansible-nas
2
0
Fork 0
mirror of https://github.com/davestephens/ansible-nas synced 2024-12-25 19:13:08 +00:00
Code Issues Projects Releases Packages Wiki Activity

Remove legacy ISSUE_TEMPLATE.md

Browse source
This commit is contained in:
David Stephens 2019-08-26 15:26:37 +01:00 committed by GitHub
parent 22b0251bf9
commit 8882851270
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 34 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
.github/ISSUE_TEMPLATE.md vendored
View file

@ -1,34 +0,0 @@
For :bug: bug reports, please fill out the information below plus any additional relevant information. For feature requests, feel free to clear the form.
If you're reporting an issue with execution of the Ansible-NAS playbook, please run the playbook with `-vvv`, and ideally isolate the problematic part with `--tags <ansible tag>` where possible.
**Short problem description**
Enter a couple of lines about the issue.
**Environment**
- Ansible-NAS revision (`git rev-parse --short HEAD`):
- Ansible version (paste the entire output of `ansible --version` on the machine you run the playbook from):
- Ansible-NAS operating system (`cat /etc/lsb-release` on the Ansible-NAS box) - _If this is anything other than Ubuntu 18.04 help will be limited_:
- Ansible-NAS kernel (`cat /etc/lsb-release` on the Ansible-NAS box):
- Ansible-NAS Python version (`python --version` on the Ansible-NAS box):
- Ansible-NAS Docker version (`docker --version` on the Ansible-NAS box):
- Latest Docker logs (`journalctl -u docker.service` on the Ansible-NAS box):
- Are you running the playbook from a remote box or the Ansible-NAS box itself?
- Vagrant version, if testing (`vagrant --version`)
**Expected behavior**
What should happen?
**Actual behavior**
What actually happens?
**Steps to reproduce**
What does someone need to do to reproduce this?
**Playbook Output**
Paste the output of the playbook at the problematic point.