Initial commit

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'Bug/Issue: '
+labels: 'bug'
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,37 @@
+---
+name: Documentation
+about: Suggest an idea for this project
+title: 'Documentation : '
+labels: documentation, question
+assignees: ''
+
+---
+
+### Problem to solve
+
+<!-- Include the following detail as necessary:
+* What project/feature(s) affected?
+* What docs or doc section affected? Include links or paths.
+* Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs?
+* Any other ideas or requests?
+-->
+
+### Further details
+
+<!--
+* Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab?
+* Include use cases, benefits, and/or goals for this work.
+* If adding content: What audience is it intended for? (What roles and scenarios?)
+-->
+
+### Proposal
+
+<!-- Further specifics for how can we solve the problem. -->
+
+### Who can address the issue
+
+<!-- What if any special expertise is required to resolve this issue? -->
+
+### Other links/references
+
+<!-- E.g. related GH issues/PRs -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'Feature request: '
+labels: 'enhancement'
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+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/pull_request_template.md

@@ -0,0 +1,24 @@
+## Describe the proposed changes included in this pull request
+
+<!-- please describte which issue or features this pull requests is addressing. and the specific changes to code branch.
+Please explain why code owner/maintanainers needs to accept the pull request.-->
+
+
+## Which issue does this pull request fix or reference?
+
+This pull request:
+
+- Resolves: {#issue-number} {Choose this option if this MR will close the issue and link to issue}
+- Relates to: {#issue-number} {Choose this option if this MR only references an issue for context but does not fully resolve it}
+
+## Checklist
+
+_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._
+
+- [ ] Lint and unit/bdd/ tests pass locally with my changes
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] Updated the README & add necessary documentation in the repo, or PR if necessary
+- [ ] Added myself / the rights holder  & update relevant licensing information as required
+
+## Further comments
+- If this is a relatively large or complex change, explain why you chose the solution you did and what alternatives you considered, etc...  If you are using the new Issue template, this suggestion was already included. If the issues you are addressing is not using the new issue template formats, then add them to this PR

.github/ISSUE_TEMPLATE/refactoring.md

@@ -0,0 +1,49 @@
+---
+name: Refactoring
+about: Suggest a refactoring for this project
+title: '[Refactoring] : '
+labels: question, enhancement
+assignees: ''
+
+---
+
+## Summary
+
+<!--
+Please briefly describe what part of the code base needs to be refactored.
+-->
+
+## Improvements
+
+<!--
+Explain the benefits of refactoring this code.
+See also https://about.gitlab.com/handbook/values/index.html#say-why-not-just-what
+-->
+
+## Risks
+
+<!--
+Please list features that can break because of this refactoring and how you intend to solve that.
+-->
+
+## Involved components
+
+<!--
+List files or directories that will be changed by the refactoring.
+-->
+
+## Optional: Intended side effects
+
+<!--
+If the refactoring involves changes apart from the main improvements (such as a better UI), list them here.
+It may be a good idea to create separate issues and link them here.
+-->
+
+
+## Optional: Missing test coverage
+
+<!--
+If you are aware of tests that need to be written or adjusted apart from unit tests for the changed components,
+please list them here.
+-->
+