Commit Graph

8 Commits

Author SHA1 Message Date
Iain Collins
4a6f153aa6 Update question.md 2020-07-10 16:14:10 +01:00
Iain Collins
9eccc78e3a Update feature_request.md 2020-07-10 16:13:12 +01:00
Iain Collins
09938cc368 Update bug_report.md 2020-07-10 16:12:59 +01:00
Iain Collins
6d1c457a75 Add action to run npm test on new pull requests 2020-06-24 02:23:48 +01:00
ndo@$(hostname)
86f0c53bd3 add: npm publish workflow 2020-06-24 01:19:51 +01:00
Iain Collins
14fd1c9b40 Update feature_request.md 2020-06-18 17:34:14 +01:00
Iain Collins
0119622d18 Update issue templates to point to documentation
Have been the asked some questions a few times (including via email).

Most of the time these reports have already been addressed.

Trying to nudge behaviour to check the example project and docs first.

Also want to understand where people couldn't find what they needed.

Removed pre-filled issue title as people were forgetting to change it.
2020-06-16 18:19:38 +01:00
Iain Collins
5fded4256d Add issue templates
Trying to create some structure to get external contributors to think about feature requests and/or provide more information when raising issues.

This is not intended for core committers - I'm just trying to wrangle the input we get to reduce signal to noise, especially as I'm also starting to get emails asking for support now.
2020-06-12 01:06:55 +01:00