chore: github setup improvements (#334)
diff --git a/.bazelversion b/.bazelversion new file mode 100644 index 0000000..bea438e --- /dev/null +++ b/.bazelversion
@@ -0,0 +1 @@ +3.3.1
diff --git a/CODEOWNERS b/.github/CODEOWNERS similarity index 100% rename from CODEOWNERS rename to .github/CODEOWNERS
diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..a8920bc --- /dev/null +++ b/.github/CODE_OF_CONDUCT.md
@@ -0,0 +1,76 @@ +# 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, 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 bazel-discuss@googlegroups.com. 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 + +For answers to common questions about this code of conduct, see +https://www.contributor-covenant.org/faq
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..697dfd5 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,76 @@ +--- +name: "\U0001F41EBug report" +about: Report a bug in rules_python +--- +<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 + +Oh hi there! 😄 + +To expedite issue processing please search open and closed issues before submitting a new one. +Existing issues often contain information about workarounds, resolution, or progress updates. + +🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅--> + + +# 🐞 bug report + +### Affected Rule + +<!-- Can you pin-point one or more rules as the source of the bug? --> +<!-- ✍️edit: --> The issue is caused by the rule: + + +### Is this a regression? + +<!-- Did this behavior use to work in the previous version? --> +<!-- ✍️--> Yes, the previous version in which this bug was not present was: .... + + +### Description + +<!-- ✍️--> A clear and concise description of the problem... + + +## 🔬 Minimal Reproduction + +<!-- +Please create and share minimal reproduction of the issue. For the purpose you can create a GitHub repository and share a link. Make sure you don't upload any confidential files. +--> + +## 🔥 Exception or Error + +<pre><code> +<!-- If the issue is accompanied by an exception or an error, please share it below: --> +<!-- ✍️--> + +</code></pre> + + +## 🌍 Your Environment + +**Operating System:** + +<pre> + <code> + + </code> +</pre> + +**Output of `bazel version`:** + +<pre> + <code> + + </code> +</pre> + +**Rules_python version:** + +<pre> + <code> + + </code> +</pre> + +**Anything else relevant?** +
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..3612d72 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,45 @@ +--- +name: "\U0001F680Feature request" +about: Suggest a feature for rules_python + +--- +<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 + +Oh hi there! 😄 + +To expedite issue processing please search open and closed issues before submitting a new one. +Existing issues often contain information about workarounds, resolution, or progress updates. + +🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅--> + + +# 🚀 feature request + +### Relevant Rules + +<!-- Tell us if you want to add a feature to an existing rule or add a new rule --> + +<!-- + +If you're looking for a new rule first make sure you check awesome-bazel for an +curated list of existing bazel rules https://github.com/jin/awesome-bazel + +If you don't find what you're looking for there, before opening a feature request make sure +this repository is the right place for that. + +--> + +### Description + +<!-- ✍️--> A clear and concise description of the problem or missing capability... + + +### Describe the solution you'd like + +<!-- ✍️--> If you have a solution in mind, please describe it. + + +### Describe alternatives you've considered + +<!-- ✍️--> Have you considered any alternative solutions or workarounds? +
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 0000000..38e0658 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,44 @@ +## PR Checklist + +Please check if your PR fulfills the following requirements: + +- [ ] Tests for the changes have been added (for bug fixes / features) +- [ ] Docs have been added / updated (for bug fixes / features) + + +## PR Type + +What kind of change does this PR introduce? + +<!-- Please check the one that applies to this PR using "x". --> + +- [ ] Bugfix +- [ ] Feature (please, look at the "Scope of the project" section in the README.md file) +- [ ] Code style update (formatting, local variables) +- [ ] Refactoring (no functional changes, no api changes) +- [ ] Build related changes +- [ ] CI related changes +- [ ] Documentation content changes +- [ ] Other... Please describe: + + +## What is the current behavior? +<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> + +Issue Number: N/A + + +## What is the new behavior? + + +## Does this PR introduce a breaking change? + +- [ ] Yes +- [ ] No + + +<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. --> + + +## Other information +