Added Github template files (#19)

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,11 @@
+# Code of Conduct
+
+## Introduction
+
+Diversity and inclusion make our community strong. We encourage participation from the most varied and diverse backgrounds possible and want to be very clear about where we stand.
+
+Our goal is to maintain a safe, helpful and friendly community for everyone, regardless of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other defining characteristic.
+
+This code and related procedures also apply to unacceptable behavior occurring outside the scope of community activities, in all community venues (online and in-person) as well as in all one-on-one communications, and anywhere such behavior has the potential to adversely affect the safety and well-being of community members.
+
+For more information on our code of conduct, please visit [https://slackhq.github.io/code-of-conduct](https://slackhq.github.io/code-of-conduct)

.github/CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributors Guide
+
+Interested in contributing? Awesome! Before you do though, please read our
+[Code of Conduct](https://slackhq.github.io/code-of-conduct). We take it very seriously, and expect that you will as
+well.
+
+There are many ways you can contribute! :heart:
+
+### Bug Reports and Fixes :bug:
+-  If you find a bug, please search for it in the [Issues](https://github.com/slackhq/tree-sitter-hack/issues), and if it isn't already tracked,
+   [create a new issue](https://github.com/slackhq/tree-sitter-hack/issues/new). Fill out the "Bug Report" section of the issue template. Even if an Issue is closed, feel free to comment and add details, it will still
+   be reviewed.
+-  Issues that have already been identified as a bug (note: able to reproduce) will be labelled `bug`.
+-  If you'd like to submit a fix for a bug, [send a Pull Request](#creating_a_pull_request) and mention the Issue number.
+  -  Include tests that isolate the bug and verifies that it was fixed.
+
+### New Features :bulb:
+-  If you'd like to add new functionality to this project, describe the problem you want to solve in a [new Issue](https://github.com/slackhq/tree-sitter-hack/issues/new).
+-  Issues that have been identified as a feature request will be labelled `enhancement`.
+-  If you'd like to implement the new feature, please wait for feedback from the project
+   maintainers before spending too much time writing the code. In some cases, `enhancement`s may
+   not align well with the project objectives at the time.
+
+### Tests :mag:, Documentation :books:, Miscellaneous :sparkles:
+-  If you'd like to improve the tests, you want to make the documentation clearer, you have an
+   alternative implementation of something that may have advantages over the way its currently
+   done, or you have any other change, we would be happy to hear about it!
+  -  If its a trivial change, go ahead and [send a Pull Request](#creating_a_pull_request) with the changes you have in mind.
+  -  If not, [open an Issue](https://github.com/slackhq/tree-sitter-hack/issues/new) to discuss the idea first.
+
+If you're new to our project and looking for some way to make your first contribution, look for
+Issues labelled `good first contribution`.
+
+## Requirements
+
+For your contribution to be accepted:
+
+- [x] You must have signed the [Contributor License Agreement (CLA)](https://cla-assistant.io/slackhq/tree-sitter-hack).
+- [x] The test suite must be complete and pass.
+- [x] The changes must be approved by code review.
+- [x] Commits should be atomic and messages must be descriptive. Related issues should be mentioned by Issue number.
+
+If the contribution doesn't meet the above criteria, you may fail our automated checks or a maintainer will discuss it with you. You can continue to improve a Pull Request by adding commits to the branch from which the PR was created.
+
+[Interested in knowing more about about pull requests at Slack?](https://slack.engineering/on-empathy-pull-requests-979e4257d158#.awxtvmb2z)
+
+## Creating a Pull Request
+
+1.  :fork_and_knife: Fork the repository on GitHub.
+2.  :runner: Clone/fetch your fork to your local development machine. It's a good idea to run the tests just
+    to make sure everything is in order.
+3.  :herb: Create a new branch and check it out.
+4.  :crystal_ball: Make your changes and commit them locally. Magic happens here!
+5.  :arrow_heading_up: Push your new branch to your fork. (e.g. `git push username fix-issue-16`).
+6.  :inbox_tray: Open a Pull Request on github.com from your new branch on your fork to `main` in this
+    repository.
+
+## Maintainers
+
+There are more details about processes and workflow in the [Maintainer's Guide](./maintainers_guide.md).

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG]"
+labels: bug
+assignees: ''
+
+---
+
+### Describe the bug
+A clear and concise description of what the bug is.
+
+### Requirements (place an `x` in each of the `[ ]`)**
+* [ ] I've read and understood the [Contributing guidelines](../CONTRIBUTING.md) and have done my best effort to follow them.
+* [ ] I've read and agree to the [Code of Conduct](https://slackhq.github.io/code-of-conduct).
+* [ ] I've searched for any related issues and avoided creating a duplicate issue.
+
+### To Reproduce
+Steps to reproduce the behavior:
+
+### Expected behavior
+A clear and concise description of what you expected to happen.
+
+#### Screenshots
+If applicable, add screenshots to help explain your problem.
+
+#### Reproducible in:
+
+{project_name} version:
+
+{platform_name} version:
+
+OS version(s):
+
+#### Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Code of Conduct
+    url: https://slackhq.github.io/code-of-conduct
+    about: Code of Conduct

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[FEATURE]"
+labels: enhancement
+assignees: ''
+
+---
+
+### Description
+
+Describe your request here.
+
+### Requirements (place an `x` in each of the `[ ]`)
+* [ ] I've read and understood the [Contributing guidelines](../CONTRIBUTING.md) and have done my best effort to follow them.
+* [ ] I've read and agree to the [Code of Conduct](https://slackhq.github.io/code-of-conduct).
+* [ ] I've searched for any related issues and avoided creating a duplicate issue.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+###  Summary
+
+Describe the goal of this PR. Mention any related Issue numbers.
+
+### Requirements (place an `x` in each `[ ]`)
+
+* [ ] I've read and understood the [Contributing Guidelines](https://github.com/slackhq/tree-sitter-hack/blob/main/.github/CONTRIBUTING.md) and have done my best effort to follow them.
+* [ ] I've read and agree to the [Code of Conduct](https://slackhq.github.io/code-of-conduct).

.github/maintainers_guide.md

@@ -0,0 +1,69 @@
+# Maintainers Guide
+
+This document describes tools, tasks and workflow that one needs to be familiar with in order to effectively maintain
+this project. If you use this package within your own software as is but don't plan on modifying it, this guide is
+**not** for you.
+
+## Tools (optional)
+
+> Are there any build tools, dependencies, or other programs someone maintaining this project
+> needs to be familiar with?
+
+## Tasks
+
+### Testing
+
+> How do you run the tests?
+
+### Generating Documentation (optional)
+
+> If the documentation is generated from source, how does someone run the generation?
+> Are the docs published on a website (GitHub Pages)?
+
+### Releasing
+
+> A description of the process to make a release for this project. Do not share any secrets here.
+
+## Workflow
+
+### Versioning and Tags
+
+> Does this project use semver? What does the numbering system look like? Are releases tagged in git?
+
+### Branches
+
+> Describe any specific branching workflow. For example:
+> `main` is where active development occurs.
+> Long running branches named feature branches are occasionally created for collaboration on a feature that has a large scope (because everyone cannot push commits to another person's open Pull Request)
+> At some point in the future after a major version increment, there may be maintenance branches
+> for older major versions.
+
+### Issue Management
+
+Labels are used to run issues through an organized workflow. Here are the basic definitions:
+
+*  `bug`: A confirmed bug report. A bug is considered confirmed when reproduction steps have been
+   documented and the issue has been reproduced.
+*  `enhancement`: A feature request for something this package might not already do.
+*  `docs`: An issue that is purely about documentation work.
+*  `tests`: An issue that is purely about testing work.
+*  `needs feedback`: An issue that may have claimed to be a bug but was not reproducible, or was otherwise missing some information.
+*  `discussion`: An issue that is purely meant to hold a discussion. Typically the maintainers are looking for feedback in this issues.
+*  `question`: An issue that is like a support request because the user's usage was not correct.
+*  `semver:major|minor|patch`: Metadata about how resolving this issue would affect the version number.
+*  `security`: An issue that has special consideration for security reasons.
+*  `good first contribution`: An issue that has a well-defined relatively-small scope, with clear expectations. It helps when the testing approach is also known.
+*  `duplicate`: An issue that is functionally the same as another issue. Apply this only if you've linked the other issue by number.
+
+> You may want to add more labels for subsystems of your project, depending on how complex it is.
+
+**Triage** is the process of taking new issues that aren't yet "seen" and marking them with a basic
+level of information with labels. An issue should have **one** of the following labels applied:
+`bug`, `enhancement`, `question`, `needs feedback`, `docs`, `tests`, or `discussion`.
+
+Issues are closed when a resolution has been reached. If for any reason a closed issue seems
+relevant once again, reopening is great and better than creating a duplicate issue.
+
+## Everything else
+
+When in doubt, find the other maintainers and ask.