From 8c2618b6915a2e51c3ff232161d88a05f1b6e9ce Mon Sep 17 00:00:00 2001
From: Llewellyn van der Merwe <llewellyn@vdm.io>
Date: Tue, 21 Nov 2017 16:18:27 +0200
Subject: [PATCH] Added github help files

---
 .github/CONTRIBUTING.md          | 18 ++++++++++++++++++
 .github/ISSUE_TEMPLATE.md        | 17 +++++++++++++++++
 .github/PULL_REQUEST_TEMPLATE.md | 20 ++++++++++++++++++++
 .github/SUPPORT.md               |  8 ++++++++
 4 files changed, 63 insertions(+)
 create mode 100644 .github/CONTRIBUTING.md
 create mode 100644 .github/ISSUE_TEMPLATE.md
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md
 create mode 100644 .github/SUPPORT.md

diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
new file mode 100644
index 000000000..108af23b7
--- /dev/null
+++ b/.github/CONTRIBUTING.md
@@ -0,0 +1,18 @@
+Contributing to the Joomla Component Builder (JCB)
+===============
+You are welcome to submit a contribution for review and possible inclusion in the Joomla Component Builder but, before it will be accepted, we ask that you follow these simple steps:
+
+1) Open an issue on GitHub. If you can, please provide a fix and create a pull request (PR) instead; this will automatically create an issue for you so you do not have to create an issue if you are creating a pull request.
+
+2) Follow the [Joomla! Coding Standards](https://developer.joomla.org/coding-standards.html).
+
+3) When filing an issue or opening a PR, please include a clear title and description. The title should be a short summary of an issue and, if possible, should include a reference to an open issue. For example, `Invalid Query in com_admin (Ref #1234)` would be sufficient. All issues and PRs should include a description with as much detail as possible. 
+If it is a PR, include what the issue is, what the PR is addressing, testing instructions and environmental information (PHP version, database driver and version, and other data you can retrieve from your site's system information view) in case the issue is specific to certain environments. If additional information is needed, please be prepared to provide it as our community members review your submission.
+
+4) Report security issues to the JCB! Core Team using the [Report security issues contact form](https://www.vdm.io/report-security-issues). Please do not use the public forums for security issues.
+
+Please be patient as not all items will be tested immediately (remember, all bug testing for the JCB is done by volunteers) and be receptive to feedback about your code.
+
+#### Branches
+PRs should usually be made to the `staging` branch as this contains the most recent version of the code.
+
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 000000000..123e4cc01
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,17 @@
+### Steps to reproduce the issue
+
+
+
+### Expected result
+
+
+
+### Actual result
+
+
+
+### System information (as much as possible)
+
+
+
+### Additional comments
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 000000000..f4fe8a2a7
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,20 @@
+Pull Request for Issue # .
+
+### Summary of Changes
+
+
+
+### Testing Instructions
+
+
+
+### Expected result
+
+
+
+### Actual result
+
+
+
+### Documentation Changes Required
+
diff --git a/.github/SUPPORT.md b/.github/SUPPORT.md
new file mode 100644
index 000000000..306bb3c21
--- /dev/null
+++ b/.github/SUPPORT.md
@@ -0,0 +1,8 @@
+Where can you get support and help?
+====================
+* [The JCB Tutorials](https://www.youtube.com/playlist?list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE);
+* [Hello World Tutorial](https://www.youtube.com/watch?v=IQfsLYIeblk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&index=45);
+* [The JCB! Wiki](https://github.com/vdm-io/Joomla-Component-Builder/wiki);
+* [JCB Google Group](https://groups.google.com/a/vdm.io/d/forum/jcb);
+* [Report a Security Issue](https://www.vdm.io/report-security-issues).
+