Github repository configuration from Sylius/Sylius

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @Sylius/core-team

.github/CONTRIBUTING.md

@@ -0,0 +1,14 @@
+Contributing Patches and BDD Methodology
+========================================
+
+Sylius is a Open Source project driven by the community. 
+Join our amazing adventure and we promise to be nice and welcoming to everyone. 
+Remember, you do not have to be a Symfony guru or even a programmer to help!
+
+You can learn [how to contribute the patches](http://docs.sylius.com/en/latest/contributing/code/patches.html)
+in our [Contributing Guide](http://docs.sylius.com/en/latest/contributing/index.html).
+
+Security Issues
+---------------
+
+We treat security very seriously, you can read about security procedures [here](http://docs.sylius.com/en/latest/contributing/code/security.html).

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,11 @@
+| Q                | A
+| ---------------- | -----
+| Bug report?      | no/yes
+| Feature request? | no/yes
+| BC Break report? | no/yes
+| RFC?             | no/yes
+| Sylius version   | 1.x.y
+
+<!--
+ - For support requests and how-tos, visit http://docs.sylius.com/en/latest/support/
+-->

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,17 @@
+---
+name: "Bug Report 🐛"
+about: Report a problem or error
+
+---
+
+
+**Sylius version affected**: 1.x.y
+
+**Description**  
+<!-- A clear and concise description of the bug you are experiencing. -->
+
+**Steps to reproduce**  
+<!-- Code and/or configuration required to reproduce the bug. -->
+
+**Possible Solution**  
+<!--- Optional: if you have any suggestions on a fix/reason for the bug -->

.github/ISSUE_TEMPLATE/documentation-issue.md

@@ -0,0 +1,10 @@
+---
+name: "Documentation Issue 📖"
+about: Report missing or bugged documentation
+
+---
+
+**Sylius docs version**: 1.x / latest
+
+**Description**
+<!-- Describe what is missing or where exactly is the bug/typo/issue located. Links highly appreciated. --!>

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,14 @@
+---
+name: Feature request ✅
+about: Suggest an idea for a feature or improvement
+
+---
+
+**Describe the proposed solution**
+<!-- A clear and concise description of what you want to happen. --!>
+
+**Describe alternatives you've considered**
+<!-- A clear and concise description of any alternative solutions or features you've considered. --!>
+
+**Additional context**
+<!-- Add any other context or screenshots about the feature request here. --!>

.github/ISSUE_TEMPLATE/security-issue.md

@@ -0,0 +1,8 @@
+---
+name: "Security Issue 🔐"
+about: Please contact us at [email protected]
+
+---
+
+If you think that you have found a security issue in Sylius, please do not use the issue tracker and do not post it publicly. 
+Instead, all security issues must be sent to `[email protected]`.

.github/ISSUE_TEMPLATE/support-question.md

@@ -0,0 +1,12 @@
+---
+name: "Support Question 🚫"
+about: See http://docs.sylius.com/en/latest/support/index.html for questions about
+  using Sylius
+
+---
+
+We use GitHub issues only to discuss about Sylius bugs, new features and documentation. 
+For this kind of questions about Sylius usage, please use
+any of the support alternatives described here: http://docs.sylius.com/en/latest/support/index.html
+
+Thank you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+| Q               | A
+| --------------- | -----
+| Branch?         | 1.5, 1.6 or master <!-- see the comment below -->
+| Bug fix?        | no/yes
+| New feature?    | no/yes
+| BC breaks?      | no/yes
+| Deprecations?   | no/yes <!-- don't forget to update the UPGRADE-*.md file -->
+| Related tickets | fixes #X, partially #Y, mentioned in #Z
+| License         | MIT
+
+<!--
+ - Bug fixes must be submitted against the 1.5 or 1.6 branch (the lowest possible)
+ - Features and deprecations must be submitted against the master branch
+ - Make sure that the correct base branch is set
+-->