💬 Adds github templates

This commit is contained in:
2019-11-30 20:09:58 +02:00
parent 827f44ac05
commit 412d6c58c0
6 changed files with 161 additions and 0 deletions

1
.github/CODEOWNERS vendored Normal file
View File

@ -0,0 +1 @@
*.cs @akritikos

76
.github/CODE_OF_CONDUCT.md vendored Normal file
View File

@ -0,0 +1,76 @@
# 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, sex characteristics, 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 [akritikos@nessos.gr](mailto:akritikos@nessos.gr). 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](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)
[homepage]: https://www.contributor-covenant.org
For answers to common questions about this code of conduct, see
[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq)

39
.github/ISSUE_TEMPLATE/BUG_REPORT.md vendored Normal file
View File

@ -0,0 +1,39 @@
---
name: "\U0001F41B Bug Report"
about: "If something isn't working as expected."
title: ''
labels: 'i: bug, i: needs triage'
assignees: 'akritikos'
---
## Bug Report
Clean up this template after reading it and provide relevant information about the bug you're reporting!
## Prerequisites
* [ ] Can you reproduce the problem in a deterministic way?
* [ ] Are you running the latest version?
* [ ] Are you reporting to the correct repository?
* [ ] Did you perform a cursory search?
## Current Behavior
A clear and concise description of the behavior.
## Expected behavior/code
A clear and concise description of what you expected to happen (or code).
### Environment
* Operating System
* .NET core version
### Possible Solution
`Only if you have suggestions on a fix for the bug`
### Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.

View File

@ -0,0 +1,24 @@
---
name: "\U0001F680 Feature Request"
about: "I have a suggestion (and may want to implement it)!"
title: ''
labels: 'i: enhancement, i: needs triage'
assignees: 'akritikos'
---
## Feature Request
Clean up this template after reading it and provide relevant information about the bug you're requesting!
## Is your feature request related to a problem?
A clear and concise description of what the problem is.
`I have an issue when [...]`
## Describe the feature you'd like
A clear and concise description of what you want to happen. Add any considered drawbacks.
## Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

1
.github/ISSUE_TEMPLATE/config.yml vendored Normal file
View File

@ -0,0 +1 @@
blank_issues_enabled: false

20
.github/PULL_REQUEST_TEMPLATE.md vendored Normal file
View File

@ -0,0 +1,20 @@
# Pull Request Template
Clean up this template and provide relevant information about your pull request!
## All Submissions
* [ ] Have you followed the guidelines in our [Contributing](../.github/CONTRIBUTING.md) document?
* [ ] Have you checked to ensure there aren't other open [Pull Requests](../../../pulls) for the same update/change?
* [ ] Does your pull request target an open issue?
### New Feature Submissions
* [ ] Does your submission pass tests?
* [ ] Have you lint your code locally prior to submission?
### Changes to Core Features
* [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
* [ ] Have you written new tests for your core changes, as applicable?
* [ ] Have you successfully ran tests with your changes locally?