merge pockethub/PocketHub to proggit/android

.gitignore

@@ -127,3 +127,6 @@ tmp/
 
 # TeXlipse plugin
 .texlipse
+
+#GitHub application codes (local and personal)
+github.properties

.travis.yml

@@ -1,19 +1,25 @@
 language: android
 android:
    components:
+   - tools
+   - tools #Running this twice get's the latest build tools (https://github.com/codepath/android_guides/wiki/Setting-up-Travis-CI)
    - platform-tools
-   - android-22
-   - build-tools-22.0.1
+   - android-28
+   - build-tools-28.0.3
    - extra
+   licenses:
+   - 'android-sdk-license-.+'
 
-jdk: oraclejdk7
+jdk: oraclejdk8
 
 notifications:
   email: false
 
+sudo: required #The build runs out of memory and is killed if we use the container system
+
 before_install:
-  - sudo apt-get update -qq
-  - if [ `uname -m` = x86_64 ]; then sudo apt-get install -qq --force-yes libgd2-xpm ia32-libs ia32-libs-multiarch > /dev/null; fi
+  - yes | sdkmanager "platforms;android-28"
 
 script:
   - ./gradlew clean build
+  - ./gradlew test

CONTRIBUTING.md

@@ -0,0 +1,36 @@
+Contributing
+============
+
+## Reporting issues
+
+* IMPORTANT: Any issues reported regarding the old Play Store version of the original GitHub app will be closed without investigation. Please only report issues regarding the current repo version (i.e. you must confirm this issue exists in the latest master). This is a different app now, and many old issues with the original app (such as 2FA) were resolved in master but not released.
+* Make sure there's not already an issue (open or closed) regarding your issue.
+* Include detailed information and steps to reproduce. Any issues opened with no description will be ignored.
+* Include a screenshot(s) of the issue. Brownie points for a screen recording of the issue.
+
+## ALL pull requests
+
+Please include a descriptive title and description. If you changed anything with the UI, please include screenshots of how
+it looks. Use descriptive messages for your commits, and be sure to explain the *why* for commits where appropriate.
+
+Please **don't** squash all your commits into one before opening the PR. Commits are easier to review when they're split up and in the
+order they happened. Of course, do squash smaller commits together as needed to ensure a clean history.
+
+If you open a pull request, you are responsible for engaging with us in the review and discussion afterward. If you don't respond
+to comments after opening, we will probably just close it.
+
+## Translations
+
+Always welcome, but please be prepared to have someone else that speaks if available to review it. Chances are that we cannot
+review it ourselves, for obvious reasons.
+
+## Bugfixes for existing issues
+
+Always welcome. Please reference the issue number you're addressing in the PR, and let us know in the issue tracker if
+you're working on it.
+
+## New features, UI changes, and infrastructure changes
+
+Please make sure you discuss these with us in the issue tracker before opening a pull request. It's good to get a conversation
+going first to make sure that everyone is on the same page, and this way you don't accidentally invest a lot of time into
+something we don't want to merge. That said, we're always open to these, so please don't hesitate to start the discussion!

ISSUE_TEMPLATE.md

@@ -0,0 +1,23 @@
+## If the issues at hand is a BUG, please follow this template. Otherwise feel free to ignore it.
+
+## Description
+A concise description of what the problem is.
+
+### Versions and device
+What version of the app does this happen on?\
+Was the version downloaded from the Play Store?\
+What version of Android does it happen on?\
+What model of phone does it happen on?
+
+## Steps to Reproduce
+1. Step by step instructions on how to reproduce this bug.
+2. The more detailed your list of instructions, the easier it is for the developer to track down the problem!
+
+### Actual behaviour
+Describe what happens when you perform the steps above.
+
+### Expected behaviour
+Describe what you expected to happen when performing the steps above.
+
+## Logs
+Please include any relevant log output that might assist in tracking down the problem.