Verified Commit a5fff60e authored by Ayush Shrivastava's avatar Ayush Shrivastava
Browse files

added MR & Issue templates

parent 37fac151
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->
<!-- like: irdest-core | hubd | alexandria | libopus-sys | android-tracing | android-client etc. -->
**To Reproduce**
Steps to reproduce the behavior:
**Expected behavior**
<!-- A clear and concise description of what you expected to happen. -->
**Screenshots(If Applicable)**
<!-- If applicable, add screenshots to help explain your problem. -->
<!-- Device: -->
**Additional context**
<!-- Add any other context that could be from past issues/MRs about the problem here. -->
**Component whose code/documentation can be Enhanced**
<!-- Select one out of code/documentation and delete the another one -->
**Proposed Enhancements**
\ No newline at end of file
**Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of the problem/new feature. -->
**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. -->
**Describe the topic to be researched**
<!-- Include any background information and available resources. -->
**Describe the goal/component for which the research is needed**
<!-- A clear and concise description of for which component/goal is the research needed -->
<!-- Checklist for reporting a bug
- Check the issue tracker. The issue you have may have already been reported.
- Ensure that you are using the latest developers version.
- Make sure that the tests are not for any other framework libraries that are being used in the code.
- Prefer code that seems to get changed by different developers and accessed by a lot of other modules.
**Type of Test**
<!-- Unit Test or UI Test -->
* [ ] Unit Test
* [ ] Integration Test
* [ ] UI Test
**Particular area and files to be tested**
**Current Status of the tests**
<!-- Are there any tests included for this particular area, which need improvement, or has this are never been tested at all? -->
**Particular Behaviour to be tested**
<!-- Give a brief description of the particular cases which need to be tested.
(For example: test whether data is saved in the database on clicking a particular button, or test whether the default language is preselected, etc) -->
\ No newline at end of file
Fixes #[issue number]
<!-- NOTE: Each MR should be linked to an Issue exempting cases of highly trivial MRs -->
<!-- Clear and concise code change description. Also, you can include checklist of changes made if the MR is large -->
**Alternative(s) considered**
<!-- Have you considered any alternatives? And if so, why have you chosen the approach in this PR? -->
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Other)
**Screenshots (if applicable)**
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment