[Doc] Add issue template

[AmirAbrams]

What is the purpose of this pull request (PR)?

Adds an issue template.

Any background context to help the reviewer?

Issue templates are new to Github and not yet implemented in this repo: Github issue-template

Example Issue Template:

Describe the issue

This is an example issue.

Is the issue reproducible? Yes

List steps to reproduce below:

1. Open Qt wallet
2. Open Menu...
3. Press test button

Expected behavior

This is just an example.

Actual behavior

This is just an example.

Any information in the debug.log file related to this issue?

Example data:
2016-08-10 05:16:25 keypool added key 135, size=135

Screenshots (if available)

N/A

What binary version was used (official or self compiled)

official binary version 0.12.

Machine specs: CPU, RAM, Disk space & OS (Windows, OS X, Linux)

Linux (Ubuntu) 16.04 64 bit, 2x vCPU, 2 TB disk and 6 GB RAM.

[btcdrak]

We definitely need something like this for issues so people can more accurately report bugs.

[AmirAbrams]

Added an issue template as well.

[jonasschnelli]

I think we should add this to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md (this page is referred to while creating an issue or PR).

[maflcko]

@jonasschnelli I am assuming GitHub will auto-fill the body of the pull or issue with this template, so you don't need to refer to it.

[maflcko]

We usually put Fixes #---- in the body of the pull to indicate that an open issue is resolved. Not sure if having a section for this in every pull makes sense.

[AmirAbrams]

I will add the Fixes # to the PR template and squash my commits into one.

Is this something you want to implement (ACK or NACK)?

[fanquake]

@AmirAbrams It is something worth adding, but make the fixes you've mentioned before asking for ACK/NACKS.

[AmirAbrams]

@fanquake, I made the requested change and squashed my commits into one.

You can test these templates by adding an issue or PR to my forked Bitcoin repo: https://github.com/amirabrams/bitcoin

Please let me know if there are any more changes you need to these templates. Thanks!

[arowser]

Can one of the admins verify this patch?

[fanquake]

PR Template:

• mention adding [skip-ci] so that trivial/doc only changes don't get run on Travis.
• You can probably remove the more-questions section
• Add a note about adding [doc] or [RPC] etc to the title.
• Screenshots can be added, they are necessary for GUI changes.
• Could have a what machines/os have you tested/compiled this code?

Issue Template:

• What version of bitcoin-core are you using? Official release or self-compiled?
• Basic specs, such as disk space and available ram.

Looks like we can also stash these files, as well as contributing.md in a hidden .github dir if we don't want to clutter the repo root.

[maflcko]

mention adding [skip-ci] so that trivial/doc only changes don't get run on Travis.

It now has to be somewhere in the commit body instead of just the GitHub pull. Taking into account that travis is now pretty fast due to efficient caching, it may not be worth to mention it in the template.

In general I am not in favor of adding too much to the pull request template, because stuff that is not relevant has to be deleted every time a pull is created. I may even prefer no pull request template at all.

[AmirAbrams]

@fanquake, I will make your requested changes, move the templates to a hidden .githubdirectory and squash my commits but don't want to waist time if the Bitcoin team does not want to implement these github templates.

@MarcoFalke, please let me know how you want to proceed with this PR.

Thanks!

[maflcko]

I think having an issue template makes sense to preempt #8130 (comment) et al.

I am not convinced about the pull template, but I am happy to hear other opinions. (Preferably by people who regularly create pulls)

[paveljanik]

I do not think PR template is needed. But for Issue, it is OK!

[fanquake]

@AmirAbrams Consensus seems to be to add just an issue template, can you update this pull?

I'd also suggest adding bitcoin specific sections to the issue template, such as

• Is the issue reproducible?
• Binary verrsion and wether it's offical or self compiled.
• Machine specs: CPU, RAM, Disk space & type etc
• Debug log

[AmirAbrams]

Yes, I will update the commit with your changes.

[maflcko]

Nit: Our preference is to use present-tense, imperative-style commit messages. (The default for git)

[maflcko]

utACK 3897668

[laanwj]

utACK 3897668