chore: repo init

Author: FantasticFiasco

.editorconfig

@@ -0,0 +1,8 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+
+[*.{csproj,json,yml}]
+indent_size = 2

.gitattributes

@@ -0,0 +1,3 @@
+# Auto detect text files and perform LF normalization
+
+* text=auto

.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 [INSERT EMAIL ADDRESS]. 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,74 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
+
+Please note we have a [code of conduct](./CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. Run tests and ensure that they all pass
+2. Ensure that ReSharper report no errors
+3. Rebase and squash your commits with meaningful commit messages
+
+## Commit Messages
+
+Format of the commit message:
+```
+<type>(<scope>): <subject>
+
+<body>
+
+<footer>
+```
+
+### Message subject (first line)
+
+The first line cannot be longer than 70 characters, the second line is always blank and other lines should be wrapped at 80 characters. The type and scope should always be lowercase as shown below.
+
+#### Allowed `<type>` values:
+
+- __feat__ - new feature for the user, not a new feature for build script
+- __fix__ - bug fix for the user, not a fix to a build script
+- __docs__ - changes to the documentation
+- __style__ - formatting, missing semi colons, etc; no production code change
+- __refactor__ - refactoring production code, eg. renaming a variable
+- __test__ - adding missing tests, refactoring tests; no production code change
+- __chore__ - updating grunt tasks etc; no production code change
+
+#### Example `<scope>` values:
+
+- init
+- runner
+- watcher
+- config
+- web-server
+- proxy
+- etc.
+
+The `<scope>` can be empty (e.g. if the change is a global or difficult to assign to a single component), in which case the parentheses are omitted.
+
+### Message body
+
+- uses the imperative, present tense: "change" not "changed" nor "changes"
+- includes motivation for the change and contrasts with previous behavior
+
+For more info about message body, see:
+
+- http://365git.tumblr.com/post/3308646748/writing-git-commit-messages
+- http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+
+### Message footer
+
+#### Referencing issues
+
+Closed issues should be listed on a separate line in the footer prefixed with "Closes" keyword like this:
+
+```
+Closes #234
+```
+
+or in the case of multiple issues:
+
+```
+Closes #123, #245, #992
+```

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,19 @@
+### Step 1: Describe your environment
+
+* Operating system?
+  
+### Step 2: Describe the problem
+
+#### Steps to reproduce:
+
+1. ___
+2. ___
+3. ___
+  
+#### Observed results
+
+* What happened? This could be a description, log output, etc.
+  
+#### Expected results
+
+* What did you expect to happen?