Added an ISSUE_TEMPLATE.md for issues

[Gum-Joe]

Hi,
I've added an issue template for issues.
If you want me to, I can add an CONTRIBUTING.md or pull request template.
Feel free to check the issue template out and make any modifications if needed.

Hope this gets merged!
P.S. Great Project!

[Gum-Joe]

Just realised: Need to add a script to remove the template, as it is not for everyone. Please do not merge.

[sahat]

Thanks @Gum-Joe, will wait on your changes.

[Gum-Joe]

Thanks for being patient @sahat

[execat]

Correct how "Jekyll" is spelled please.

[Gum-Joe]

Ok

[Gum-Joe]

@sahat I've added all my commits. As there are no conflicts, you can safely to merge this pull request.
Notes on the bootstrap script:

• I have stored it in generators/util/bootstrap.js. It is ran by script/bootstrap.
• As I did not know where to put generators/util/bootstrap.js to be ran, I created script/bootstrap to bootstrap on npm install, but did not add it as a script in case it ruined the development environment.
• You could add generators/util/bootstrap.js as a script ran after a generator.
• I created the generators/util directory to store the utils for generating in. You may want to separate out generators/utils.js into separate files in generators/util
• The script can also be used to make files:

// File generators/util/bootstrap.js
// Files to make
const newfiles = [
  // Place file names in this format:
  // { name: 'file', content: 'file' }
];

[execat]

Thanks!

[Gum-Joe]

@execat Your welcome

[Gum-Joe]

Hi,
This pull request has been open for 2 weeks, yet not merged. Is there anything missing?

[sahat]

@Gum-Joe Hey, I was just a little confused with the bootstrap function, how is it related to ISSUE_TEMPLATE.md?

Also, I am kind of new to these GitHub templates. Is there any way for me to test it before merging?

[Gum-Joe]

@sahat First of all, I am very sorry for being impatient and wanting my pull request to be merged quite quickly.

The bootstrap function is supposed to remove files that the end user (the one generating the boiler plate) does not need, in this case ISSUE_TEMPLATE.md, as it is for this repo (sahat/megaboilerplate). Also, it create new files for the end user, such as a minimal CONTRIBUTING.md.

Testing ISSUE_TEMPLATE.md is a bit tedious. First, open up a new repo (make sure to give it a description that tells the user to ignore the repo) or make a private repo if you are on a plan, then copy the contents of ISSUE_TEMPLATE.md into a new ISSUE_TEMPLATE.md in that repo. Commit the file. Open up a issue, and you should see it already filled. If you go through it, you should see check boxes and commented instructions on what to do. Complete the template as if you are making an issue yourself for your repo. To check the formatting, click the preview button. All the comments should not appear, the info should be in place and some of the check boxes should be ticked.

[Gum-Joe]

Hello @sahat. It's been ~1.5 years since this PR was opened and nothing has happened since. Is it worth keeping this PR open, or should it be closed?