iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

contributing: clarify how to submit debug output with a new issue

This commit is contained in:
Jack Pearkes 2013-10-18 10:04:33 +02:00
parent 934e124719
commit 0f7f0e29a6
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -18,6 +18,12 @@ it raises the chances we can quickly merge or address your contributions.
* Make sure you test against the latest released version. It is possible * Make sure you test against the latest released version. It is possible
we already fixed the bug you're experiencing. we already fixed the bug you're experiencing.
* Run the command with debug ouput with the environment variable
`PACKER_LOG`. For example: `PACKER_LOG=1 packer build template.json`. Take
the *entire* output and create a [gist](https://gist.github.com) for linking
to in your issue. Packer should strip sensitive keys from the output,
but take a look through just in case.
* Provide a reproducible test case. If a contributor can't reproduce an * Provide a reproducible test case. If a contributor can't reproduce an
issue, then it dramatically lowers the chances it'll get fixed. And in issue, then it dramatically lowers the chances it'll get fixed. And in
some cases, the issue will eventually be closed. some cases, the issue will eventually be closed.