Add GitHub configurations

.github/CODEOWNERS

@@ -0,0 +1,16 @@
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+
+# More details are here: https://help.github.com/articles/about-codeowners/
+
+# The '*' pattern is global owners.
+# Not adding in this PR, but I'd like to try adding a global owner set with the entire team.
+# One interpretation of their docs is that global owners are added only if not removed
+# by a more local rule.
+
+# Order is important. The last matching pattern has the most precedence.
+# The folders are ordered as follows:
+
+# In each subsection folders are ordered first by depth, then alphabetically.
+# This should make it easy to add new rules without breaking existing ones.
+*       @skydoves

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: skydoves
+custom: ["https://www.paypal.me/skydoves", "https://www.buymeacoffee.com/skydoves"]

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,17 @@
+---
+name: Bug report
+about: Something is crashing or not working as intended
+
+---
+
+**Please complete the following information:**
+- Library Version [e.g. v1.0.0]
+- Affected Device(s) [e.g. Samsung Galaxy s10 with Android 9.0]
+
+**Describe the Bug:**
+
+Add a clear description about the problem.
+
+**Expected Behavior:**
+
+A clear description of what you expected to happen.

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem?**
+
+A clear and concise description of what the problem is.
+
+**Describe the solution you'd like:**
+
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered:**
+
+A clear description of any alternative solutions you've considered.

.github/pull_request_template.md

@@ -0,0 +1,18 @@
+## Guidelines
+Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
+
+### Types of changes
+What types of changes does your code introduce?
+
+- [ ] Bugfix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+### Preparing a pull request for review
+Ensure your change is properly formatted by running:
+
+```gradle
+$ ./gradlew spotlessApply
+```
+
+Please correct any failures before requesting a review.

.github/workflows/android.yml

@@ -0,0 +1,25 @@
+name: Android CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: set up JDK 1.8
+        uses: actions/setup-java@v1
+        with:
+          java-version: 1.8
+      - name: Make Gradle executable
+        run: chmod +x ./gradlew
+      - name: Build with Gradle
+        run: ./gradlew build
+      - name: Build Debug APK
+        run: ./gradlew assembleDebug