packer-cn/.github/ISSUE_TEMPLATE.md

_Please read these instructions before submitting_

**DELETE THIS TEMPLATE BEFORE SUBMITTING**

_Only use GitHub issues to report bugs or feature requests, see
https://www.packer.io/community.html_

For example, _Timeouts waiting for SSH/WinRM_ are generally not bugs within packer and are better addressed by the mailing list. Ask on the mailing list if you are unsure.

If you are planning to open a pull-request just open the pull-request instead of making an issue first.

FOR FEATURES:

Describe the feature you want and your use case _clearly_.

FOR BUGS:

Describe the problem and include the following information:

- Packer version from `packer version`
- Host platform
- Debug log output from `PACKER_LOG=1 packer build template.json`.
  Please paste this in a gist https://gist.github.com
- The _simplest example template and scripts_ needed to reproduce the bug.
  Include these in your gist https://gist.github.com
Updated ISSUE_TEMPLATE.md 2017-06-28 01:39:26 -04:00			`_Please read these instructions before submitting_`
Deflect some issues which are not bugs I think we should make it more clear that connection issues are generally not bugs and should be sent to the mailing list or IRC etc. What do you think? 2017-06-27 09:32:52 -04:00
Emphasise that the template should be removed before submitting. 2016-03-07 06:05:59 -05:00			`DELETE THIS TEMPLATE BEFORE SUBMITTING`

Miscellaneous doc improvements backticks, spaces, commas In general, a list of items should have a space after each comma. While there are editorial styles that suggest commas inside quotations, they're horrible advice when the backticks are describing specific character for a user to enter. one off indent filters section singular backticks... word wrap long lines... spelling: macOS contributing: clarify closing case contributing: link to changelog contributing: point to git remote... contributing: split commands from descriptions contributing: grammar spelling: github grammar: comma after etc. spelling: macOS grammar: i.e. alicloud: use relative link alicloud: use backticks alicloud: bits alicloud: such as grammar: comma after etc. avoid linking periods grammar: period amazon-chroot: IOPS amazon-chroot: use backticks amazon-chroot: link to section amazon-chroot: whether-or-not; period amazon-ebs: period amazon-ebs: use relative link amazon-ebs: use backticks amazon-ebs: comma amazon-ebs: bold amazon-ebssurrogate: comma after etc. amazon-ebssurrogate: this builder amazon-instance: this builder amazon-ebssurrogate: set this amazon-ebssurrogate: whether-or-not amazon-ebssurrogate: period amazon-ebssurrogate: bold section reference amazon-ebssurrogate: backticks... amazon-ebssurrogate: commas around e.g. spelling: precedence spelling: i.e. amazon-ebssurrogate: backticks... 2018-10-18 19:09:49 -04:00			`_Only use GitHub issues to report bugs or feature requests, see`
fix link in issue template 2017-03-30 03:25:35 -04:00			`https://www.packer.io/community.html_`
Accept only bug reports and feature requests 2016-04-11 06:55:11 -04:00
Updated ISSUE_TEMPLATE.md 2017-06-28 01:39:26 -04:00			`For example, _Timeouts waiting for SSH/WinRM_ are generally not bugs within packer and are better addressed by the mailing list. Ask on the mailing list if you are unsure.`
Deflect some issues which are not bugs I think we should make it more clear that connection issues are generally not bugs and should be sent to the mailing list or IRC etc. What do you think? 2017-06-27 09:32:52 -04:00
Trim the pull request template 2016-03-01 22:31:07 -05:00			`If you are planning to open a pull-request just open the pull-request instead of making an issue first.`

Added github issue and PR templates 2016-02-24 20:41:57 -05:00			`FOR FEATURES:`

Emphasise that the template should be removed before submitting. 2016-03-07 06:05:59 -05:00			`Describe the feature you want and your use case _clearly_.`
Added github issue and PR templates 2016-02-24 20:41:57 -05:00
			`FOR BUGS:`

			`Describe the problem and include the following information:`

Clearified how to specify version when reporting issues 2016-08-25 02:46:42 -04:00			- Packer version from `packer version`
Added github issue and PR templates 2016-02-24 20:41:57 -05:00			`- Host platform`
Remove errant e 2016-02-26 13:47:29 -05:00			- Debug log output from `PACKER_LOG=1 packer build template.json`.
Added github issue and PR templates 2016-02-24 20:41:57 -05:00			`Please paste this in a gist https://gist.github.com`
Emphasise that the template should be removed before submitting. 2016-03-07 06:05:59 -05:00			`- The _simplest example template and scripts_ needed to reproduce the bug.`
Added github issue and PR templates 2016-02-24 20:41:57 -05:00			`Include these in your gist https://gist.github.com`
Updated ISSUE_TEMPLATE.md 2017-06-28 01:39:26 -04:00