diff options
| author | Lamont Granquist <lamont@scriptkiddie.org> | 2016-02-17 11:29:29 -0800 |
|---|---|---|
| committer | Lamont Granquist <lamont@scriptkiddie.org> | 2016-02-17 11:29:29 -0800 |
| commit | df1205046e1ac09ff6c5640a1d21d147d191cac9 (patch) | |
| tree | 094b7f734b4ba4ac6987b53bf27c9136317e5b10 | |
| parent | e48aee5eae2191cf5755697d3f4407827945b0e9 (diff) | |
| download | chef-df1205046e1ac09ff6c5640a1d21d147d191cac9.tar.gz | |
add an issue template
See https://github.com/dear-github/dear-github/issues/125
I think this keeps the ask fairly doable, while making sure to
cover the bases that we need covered 90+% of the time.
| -rw-r--r-- | issue_template.md | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/issue_template.md b/issue_template.md new file mode 100644 index 0000000000..d8b72f127a --- /dev/null +++ b/issue_template.md @@ -0,0 +1,29 @@ +## Description + +Briefly describe the issue + +## Chef Version + +Tell us which version of chef-client you are using (This repo is only for chef-client bugs). + +## Platform Version + +Tell us which Operating System distribution and version chef-client is running on. + +## Replication Case + +Tell us what steps to take to replicate your problem. See [How to create a Minimal, Complete, and Verifiable example](https://stackoverflow.com/help/mcve) +for information on how to create a good replication case. + +## Error Output + +The complete output of the chef-client run or a link to a gist of it, if there is one. + +## Stacktrace + +Please include the stacktrace.out output or link to a gist of it, if there is one. + +### NOTE: CHEF CLIENT BUGS ONLY + +* [Server issues](https://github.com/chef/chef-server/issues/new) +* Cookbook Issues (see https://github.com/chef-cookbooks repos or search supermarket/github) |