Add bug report template for Vagrant GitHub issues

This commit is contained in:
Brian Cain 2020-03-10 09:46:31 -07:00
parent c202a675b3
commit febe17fd1e
No known key found for this signature in database
GPG Key ID: 9FC4639B2E4510A0

View File

@ -1,19 +1,29 @@
---
name: Vagrant Bug Report
about: For when Vagrant is not working as expected or you have encountered a bug
---
Please note that the Vagrant issue tracker is in priority reserved for bug reports and enhancements. For general usage questions, please use
HashiCorp Discuss: https://discuss.hashicorp.com/c/vagrant/24 Thank you!
**Tip:** Before submitting your issue, don't hesitate to remove the above introductory text, possible empty sections (e.g. References), and this tip.
### Vagrant version
Run `vagrant -v` to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.
### Host operating system
This is the operating system that you run locally.
### Guest operating system
This is the operating system you run in the virtual machine.
### Vagrantfile
```ruby
# Copy-paste your Vagrantfile here (but don't include sensitive information such as passwords, authentication tokens, or email addresses)
```
@ -23,23 +33,28 @@ may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.
### Debug output
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
### Expected behavior
What should have happened?
### Actual behavior
What actually happened?
### Steps to reproduce
1.
2.
3.
### References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
- GH-1234