Added GitHub integration

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

.github/CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Contributing
+Considering that this project is actively maintained, contributions of all types are welcome.
+
+
+## Opening issues
+Open a new issue when:
+- you notice an unwanted behavior
+- you want a new feature implemented
+- you have just some doubts
+
+To open a new issue, please use the provided issue template and fill it out as much as possible.
+If you are interested to an existing issue, feel free to comment the issue or subscribe to it.
+
+
+## Submitting pull requests
+If you want to fix a bug or implement a new feature, feel free to submit a new pull request.
+To submit a pull request, you have to fork this repository and fill the PR template.
+When you want to submit a pull request, remember to:
+- follow this project's code style
+- run `./gradlew clean check`

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,57 @@
+<!--
+Any HTML comment will be stripped when the markdown is rendered, so you don't need to delete them.
+
+Put an x inside the [] like this: [x] to mark the checkbox.
+-->
+### Step 1: Are you in the right place?
+- [ ] I have verified there are no duplicate active or recent bugs, questions, or requests
+- [ ] I have verified that I am using the latest version of the plugin.
+
+### Step 2: Describe your environment
+ - Plugin version: `?`
+ - PyCharm/IDEA version: `?`
+ - Pylint version: `?`
+
+### Step 3: Describe the problem:
+#### Steps to reproduce:
+
+  1. _____
+  2. _____
+  3. _____
+
+<!-- 
+What happened?  This could be a description, log output, etc.
+-->
+#### Observed Results:
+
+  * 
+
+<!-- 
+What did you expect to happen?
+-->
+#### Expected Results:
+
+  * 
+
+#### Relevant Code:
+<!--
+Please wrap code with correct syntax highlighting.
+-->
+```java
+System.out.println("Hello, world!");
+```
+
+<!--
+If you are getting an error in the Event Log, paste it here.
+Please wrap logs with Gradle syntax highlighting (it makes them look better).
+-->
+```Gradle
+java.lang.RuntimeException: This is an example Exception log
+    at jahirfiquitiva.libs.fabsmenu.HelloWorld
+    at jahirfiquitiva.libs.fabsmenu.HelloWorld$ThisIsNotARealLog
+    at android.app.Instrumentation.callActivityOnResume(Instrumentation.kt)
+```
+
+<!--
+Adding pictures/screenshots/videos of the expected/actual result is always helpful
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+<!--
+Any HTML comment will be stripped when the markdown is rendered, so you don't need to delete them.
+-->
+
+<!-- You can remove this first section if you have contributed before -->
+### First time contributor checklist
+<!-- replace the empty checkboxes [ ] below with checked ones [x] accordingly -->
+- [ ] I have read [how to contribute](/.github/CONTRIBUTING.md) to this project
+- [ ] I have read [the code of conduct](/.github/CODE_OF_CONDUCT.md) to this project
+
+### Contributor checklist
+<!-- replace the empty checkboxes [ ] below with checked ones [x] accordingly -->
+- [ ] I am using the provided [codeStyleConfig.xml](/.idea/codeStyles)
+- [ ] I have tested my contribution on these versions of PyCharm/IDEA:
+ * PyCharm Community XXXX.Y.Z
+ * IntelliJ IDEA XXXX.Y.Z
+- [ ] My contribution is fully baked and ready to be merged as is
+- [ ] I ensure that all the open issues my contribution fixes are mentioned in the commit message of my first commit 
+      using the `Fixes #1234` [syntax](https://help.github.com/articles/closing-issues-using-keywords/)
+
+----------
+
+### Description
+<!--
+Describe briefly what your pull request proposes to fix. Especially if you have more than one commit, it is helpful to 
+give a summary of what your contribution as a whole is trying to solve.
+Also, please describe shortly how you tested that your fix actually works.
+-->

.github/ci-reporter.yml

@@ -0,0 +1,8 @@
+# Set to false to create a new comment instead of updating the app's first one
+updateComment: true
+
+# Use a custom string, or set to false to disable
+before: "Unfortunately, the [{{ provider }} build]({{ targetUrl }}) is failing as of {{ commit }}. Here's the output:"
+
+# Use a custom string, or set to false to disable
+after: "If you need help with this issue, don't hesitate to ask a maintainer of the project!"

.github/labels.json

@@ -0,0 +1,86 @@
+[
+  {
+    "name": "Priority: Critical",
+    "color": "#D32F2F"
+  },
+  {
+    "name": "Priority: High",
+    "color": "#FF9800"
+  },
+  {
+    "name": "Priority: Low",
+    "color": "#4CAF50"
+  },
+  {
+    "name": "Priority: Medium",
+    "color": "#CDDC39"
+  },
+  {
+    "name": "Status: Abandoned",
+    "color": "#000000"
+  },
+  {
+    "name": "Status: Accepted",
+    "color": "#4CAF50"
+  },
+  {
+    "name": "Status: Available",
+    "color": "#C8E6C9"
+  },
+  {
+    "name": "Status: Blocked",
+    "color": "#D32F2F"
+  },
+  {
+    "name": "Status: Completed",
+    "color": "#009688"
+  },
+  {
+    "name": "Status: In Progress",
+    "color": "#E0E0E0"
+  },
+  {
+    "name": "Status: Info needed",
+    "color": "#5C6BC0"
+  },
+  {
+    "name": "Status: On Hold",
+    "color": "#D32F2F"
+  },
+  {
+    "name": "Status: Pending",
+    "color": "#FFF176"
+  },
+  {
+    "name": "Status: Review Needed",
+    "color": "#CDDC39"
+  },
+  {
+    "name": "Status: Revision Needed",
+    "color": "#D32F2F"
+  },
+  {
+    "name": "Status: Stale",
+    "color": "#9E9E9E"
+  },
+  {
+    "name": "triage",
+    "color": "#81D4FA"
+  },
+  {
+    "name": "Type: Bug",
+    "color": "#D32F2F"
+  },
+  {
+    "name": "Type: Enhancement",
+    "color": "#546E7A"
+  },
+  {
+    "name": "Type: Maintenance",
+    "color": "#CDDC39"
+  },
+  {
+    "name": "Type: Question",
+    "color": "#673AB7"
+  }
+]

.github/no-response.yml

@@ -0,0 +1,13 @@
+# Configuration for probot-no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 21
+# Label requiring a response
+responseRequiredLabel: "Status: Info needed"
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >
+  This issue has been automatically closed because there has been no response
+  to our request for more information from the original author. With only the
+  information that is currently in the issue, we don't have enough information
+  to take action. Please reach out if you have or find the answers we need so
+  that we can investigate further.

.github/stale.yml

@@ -0,0 +1,52 @@
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 60
+
+# Number of days of inactivity before a stale Issue or Pull Request is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: false
+
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+  - pinned
+  - security
+
+# Set to true to ignore issues in a project (defaults to false)
+exemptProjects: false
+
+# Set to true to ignore issues in a milestone (defaults to false)
+exemptMilestones: false
+
+# Label to use when marking as stale
+staleLabel: "Status: Stale"
+
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had activity in the last 60 days.
+
+# Comment to post when removing the stale label.
+# unmarkComment: >
+#   Your comment here.
+
+# Comment to post when closing a stale Issue or Pull Request.
+# closeComment: >
+#   Your comment here.
+
+# Limit the number of actions per hour, from 1-30. Default is 30
+limitPerRun: 30
+
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
+# pulls:
+#   daysUntilStale: 30
+#   markComment: >
+#     This pull request has been automatically marked as stale because it has not had
+#     recent activity. It will be closed if no further activity occurs. Thank you
+#     for your contributions.
+
+# issues:
+#   exemptLabels:
+#     - confirmed

.travis.yml

@@ -0,0 +1,31 @@
+language: android
+jdk: oraclejdk8
+sudo: true
+
+os:
+  - linux
+addons:
+  apt_packages:
+    - pandoc
+
+before_cache:
+  # Do not cache a few Gradle files/directories (see https://docs.travis-ci.com/user/languages/java/#Caching)
+  - rm -f  $HOME/.gradle/caches/modules-2/modules-2.lock
+  - rm -fr $HOME/.gradle/caches/*/plugin-resolution/
+
+cache:
+  directories:
+    # Gradle dependencies
+    - $HOME/.gradle/caches/
+    - $HOME/.gradle/wrapper/
+
+script:
+  - set -o pipefail
+  - ./gradlew clean check --profile --continue 2>&1 | tee build.log
+  - set +o pipefail
+  - |
+    if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then
+      ./gradlew violationCommentsToGitHub -DGITHUB_PULLREQUESTID=$TRAVIS_PULL_REQUEST -DGITHUB_OAUTH2TOKEN=$GITHUB_OAUTH2TOKEN --info
+    fi
+  - pandoc `ls -1rt build/reports/profile/profile-*.html | tail -n1` -t plain
+  - ./gradlew dependencyUpdate

RELEASING.md

@@ -0,0 +1,15 @@
+# Releasing
+
+1. Bump the `version` property in `gradle.properties` based on Major.Minor.Patch naming scheme
+2. Update `CHANGELOG.md` for the impending release.
+3. Update the `README.md` with the new version.
+4. `./gradlew clean buildPlugin` 
+5. `git commit -am "Prepare for release X.Y.Z"` (where X.Y.Z is the version you set in step 1)
+6. `git push`
+7. `./gradlew publishPlugin`
+8. Create a new release on Github
+    1. Tag version `X.Y.Z` (`git tag -s X.Y.Z && git push --tags`)
+    2. Release title `X.Y.Z`
+    3. Paste the content from `CHANGELOG.md` as the description
+    4. Upload the `build/distributions/Pylint-X.X.X.zip`
+9. Create a PR from [master](../../tree/master) to [release](../../tree/release)