add github stuff

.github/CONTRIBUTING.md

@@ -0,0 +1,24 @@
+## Contributing 
+
+We love pull requests from everyone. 
+
+Fork, then clone the repo:
+
+```bash
+$ git clone [email protected]:your-username/allure-gradle.git
+```
+
+Then build the project (build requires JDK 1.8 or higher):
+
+```bash
+$ ./gradlew build
+```
+
+Make your change. Add tests for your change. Make sure all the tests pass:
+
+```bash
+$ ./gradlew test
+```
+
+Push your fork and submit a pull request. 
+

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,45 @@
+[//]: # (
+. Note: for support questions, please use Stackoverflow or Gitter**. 
+. This repository's issues are reserved for feature requests and bug reports.
+.
+. In case of any problems with Allure Jenkins plugin** please use the following repository 
+. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
+.
+. Make sure you have a clear name for your issue. The name should start with a capital 
+. letter and no dot is required in the end of the sentence. An example of good issue names:
+.
+. - The report is broken in IE11
+. - Add an ability to disable default plugins
+. - Support emoji in test descriptions
+)
+
+#### I'm submitting a ... 
+  - [ ] bug report
+  - [ ] feature request
+  - [ ] support request => Please do not submit support request here, see note at the top of this template.
+
+#### What is the current behavior?
+
+
+#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
+
+
+#### What is the expected behavior?
+
+
+#### What is the motivation / use case for changing the behavior?
+
+
+#### Please tell us about your environment:
+
+- Allure version:        2.1.0
+- Test framework:        [email protected]
+- Allure adaptor:        [email protected]
+- Generate report using: [email protected]
+
+#### Other information 
+
+[//]: # (
+. e.g. detailed explanation, stacktraces, related issues, suggestions 
+. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
+)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+[//]: # (
+. Thank you so much for sending us a pull request! 
+.
+. Make sure you have a clear name for your pull request. 
+. The name should start with a capital letter and no dot is required in the end of the sentence.
+. To link the request with isses use the following notation: (fixes #123, fixes #321\)
+.
+. An example of good pull request names:
+. - Add Russian translation (fixes #123\)
+. - Add an ability to disable default plugins
+. - Support emoji in test descriptions
+)
+
+### Context
+[//]: # (
+Describe the problem or feature in addition to a link to the issues
+)
+
+#### Checklist
+- [ ] [Sign Allure CLA][cla]
+- [ ] Provide unit tests
+
+[cla]: https://cla-assistant.io/accept/allure-framework/allure2

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 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, 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]. The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/