Merge pull request #28 from mohaltheeb/develop

feat(core): Adding Pull Request and Issues Templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,47 @@
+---
+name: Bug report
+about: 'Report a bug encountered while using the Academia Application to help us improve '
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+<!--
+Welcome to the Academia Application issue tracker! Before creating an issue, please heed the following:
+
+1. This tracker should only be used to report bugs and request features / enhancements to Academia Application
+    
+2. Use the search function before creating a new issue. Duplicates will be closed and directed to the original discussion.
+
+3. When making a bug report, make sure you provide all required information. The easier it is for maintainers to reproduce, the faster it'll be fixed.
+
+4. If you think you know what the reason for the bug is, share it with us. Maybe put in a Pull  Request😉
+-->
+
+## Description of the issue
+A clear and concise description of what the bug is.
+
+## Context information (for bug reports)
+
+**Output of `bench version`**
+```
+(paste here)
+```
+
+### Observed result
+
+### Expected result
+
+### Screenshots
+If applicable, add screenshots to help explain your problem.
+
+### Stacktrace / full error message
+
+```
+(paste here)
+```
+
+## Additional information
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,31 @@
+---
+name: Feature request
+about: Suggest an Idea to Improve Academia Application
+title: ''
+labels: feature-request
+assignees: ''
+
+---
+
+<!--
+Welcome to the Academia Application issue tracker! Before creating an issue, please heed the following:
+
+1. This tracker should only be used to report bugs and request features / enhancements to Academia Application
+   
+2. Use the search function before creating a new issue. Duplicates will be closed and directed to
+   the original discussion.
+
+3. When making a feature request, make sure to be as verbose as possible. The better you convey your message, the     greater the drive to make it happen.
+-->
+
+**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/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,50 @@
+<!--
+
+Some key notes before you open a PR:
+
+ 1. Select which branch should this PR be merged in?
+ 2. PR name follows [convention](http://karma-runner.github.io/4.0/dev/git-commit-msg.html)
+ 3. All tests pass locally, UI and Unit tests
+ 4. All business logic and validations must be on the server-side
+ 5. Update necessary Documentation
+ 6. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes
+
+
+Also, if you're new here
+
+- Documentation Guidelines => https://github.com/Sana-a-Uni/Academia
+
+- Contribution Guide => https://github.com/Sana-a-Uni/Academia
+
+- Pull Request Checklist => https://github.com/Sana-a-Uni/Academia
+
+-->
+
+
+
+
+### Description:
+Brief description of this pull requeste
+
+
+
+### Changes Made:
+
+> Please provide enough information so that others can review your pull request:
+
+<!-- You can skip this if you're fixing a typo or updating existing documentation -->
+
+> Explain the **details** for making this change. What existing problem does the pull request solve?
+
+<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
+
+> Screenshots/GIFs
+
+<!-- If available Add images/recordings to better visualize the change: expected/current behviour -->
+
+
+
+Reviewers: @
+
+
+