github: Added Templates for Issue and Pull Requests.

Edited by tabbott for clearer professional English.

Fixes #313.

Author: jainkuniya

.github/ISSUES_GUIDE.md

@@ -0,0 +1,13 @@
+**Writing good bug reports**
+
+- Include `LogCat` output for crashes.
+
+- Include a screenshot for UI/display issues.
+
+- Include device info (model number, Android version etc) if it could
+  be relevant.
+
+- Provide steps to reproduce if you know how to reproduce the issue.
+
+- Read more details on good bug reporting practices at
+  https://guides.github.com/features/issues/.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,13 @@
+[Read our guide on bug reports here](./ISSUES_GUIDE.md)
+
+**Actual Behaviour**
+
+Explain what is currently happening.
+
+**Expected Behaviour**
+
+Explain what you expected (unnecessary if it's obviouxly broken, e.g. a crash).
+
+**Would you like to work on the issue?**
+
+Let us know if this issue should be assigned to you.

.github/PULL_REQUEST_GUIDE.md

@@ -0,0 +1,42 @@
+**Auto-formatting code**
+
+The Zulip Android app uses auto-formatted code.  In Android Studio,
+you can auto-format code as follows:
+
+* Mac: `Option + Command + L`
+* Windows: `Ctrl + Alt + L`
+* Linux: Go to `File->Settings->(under IDE settings)->Keymap` and
+  change the shortcut as `Ctrl + Alt + L` locks the screen on linux.
+
+**Lint issues**
+
+- Run the lint tests with `./gradlew lintDebug`.
+
+- It ensure that code has no structural problems. Poorly structured
+  code can impact the reliability and efficiency of Android apps and
+  make code harder to maintain. For example, if XML resource files
+  contain unused namespaces, this takes up space and incurs
+  unnecessary processing. Other structural issues, such as use of
+  deprecated elements or API calls that are not supported by the
+  target API versions, might lead to code failing to run correctly.
+
+- If lint fails, check the report at
+  `zulip-android/app/build/outputs/lint-results-debug.html` or
+  `zulip-android/app/build/outputs/lint-results-debug.xml`
+
+**Night Mode**
+
+zulip-android contains a theme for night, so if new UI is designed or
+UI is altered, please test to make sure that it is looks good with the
+Night theme too.
+
+**Commit messages**
+
+- Usually starts with capital letter, and ends with a period.
+
+- Include `Fixes: #{issue-number}` as a sentence at the end of the
+  commit message, so that issue is automatically closed when the
+  commits are merged.
+
+- Read the Zulip project's detailed guide to writing good commits here:
+  https://zulip.readthedocs.io/en/latest/version-control.html#commit-messages

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+**Summary of changes**
+
+[Explain here what changes were made and why.]
+
+Screenshots or a brief video showing the change in action:
+
+
+Please make sure these boxes are checked before submitting your pull request - thanks! [Guide](./PULL_REQUEST_GUIDE.md)
+
+- [ ] Code is formatted.
+
+- [ ] Run the lint tests with `./gradlew lintDebug` and make sure BUILD is SUCCESSFUL
+
+- [ ] If new feature is implemeted then it is compatible with Night theme too.
+
+- [ ] Used `Zlog.logException(e)` instead of `e.printStackTrace()`
+
+- [ ] Commit messages are well-written.