Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 32e9648

Browse filesBrowse files
alexeaglealexeagle
authored
chore: github setup improvements (bazel-contrib#334)
1 parent cd55272 commit 32e9648
Copy full SHA for 32e9648

File tree

6 files changed

+242
-0
lines changed
Filter options

6 files changed

+242
-0
lines changed

‎.bazelversion

Copy file name to clipboard
+1Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
3.3.1

‎CODEOWNERS renamed to ‎.github/CODEOWNERS

Copy file name to clipboard
File renamed without changes.

‎.github/CODE_OF_CONDUCT.md

Copy file name to clipboard
+76Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at bazel-discuss@googlegroups.com. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎.github/ISSUE_TEMPLATE/bug_report.md

Copy file name to clipboard
+76Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
name: "\U0001F41EBug report"
3+
about: Report a bug in rules_python
4+
---
5+
<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
6+
7+
Oh hi there! 😄
8+
9+
To expedite issue processing please search open and closed issues before submitting a new one.
10+
Existing issues often contain information about workarounds, resolution, or progress updates.
11+
12+
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
13+
14+
15+
# 🐞 bug report
16+
17+
### Affected Rule
18+
19+
<!-- Can you pin-point one or more rules as the source of the bug? -->
20+
<!-- ✍️edit: --> The issue is caused by the rule:
21+
22+
23+
### Is this a regression?
24+
25+
<!-- Did this behavior use to work in the previous version? -->
26+
<!-- ✍️--> Yes, the previous version in which this bug was not present was: ....
27+
28+
29+
### Description
30+
31+
<!-- ✍️--> A clear and concise description of the problem...
32+
33+
34+
## 🔬 Minimal Reproduction
35+
36+
<!--
37+
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.
38+
-->
39+
40+
## 🔥 Exception or Error
41+
42+
<pre><code>
43+
<!-- If the issue is accompanied by an exception or an error, please share it below: -->
44+
<!-- ✍️-->
45+
46+
</code></pre>
47+
48+
49+
## 🌍 Your Environment
50+
51+
**Operating System:**
52+
53+
<pre>
54+
<code>
55+
56+
</code>
57+
</pre>
58+
59+
**Output of `bazel version`:**
60+
61+
<pre>
62+
<code>
63+
64+
</code>
65+
</pre>
66+
67+
**Rules_python version:**
68+
69+
<pre>
70+
<code>
71+
72+
</code>
73+
</pre>
74+
75+
**Anything else relevant?**
76+

‎.github/ISSUE_TEMPLATE/feature_request.md

Copy file name to clipboard
+45Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
name: "\U0001F680Feature request"
3+
about: Suggest a feature for rules_python
4+
5+
---
6+
<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
7+
8+
Oh hi there! 😄
9+
10+
To expedite issue processing please search open and closed issues before submitting a new one.
11+
Existing issues often contain information about workarounds, resolution, or progress updates.
12+
13+
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
14+
15+
16+
# 🚀 feature request
17+
18+
### Relevant Rules
19+
20+
<!-- Tell us if you want to add a feature to an existing rule or add a new rule -->
21+
22+
<!--
23+
24+
If you're looking for a new rule first make sure you check awesome-bazel for an
25+
curated list of existing bazel rules https://github.com/jin/awesome-bazel
26+
27+
If you don't find what you're looking for there, before opening a feature request make sure
28+
this repository is the right place for that.
29+
30+
-->
31+
32+
### Description
33+
34+
<!-- ✍️--> A clear and concise description of the problem or missing capability...
35+
36+
37+
### Describe the solution you'd like
38+
39+
<!-- ✍️--> If you have a solution in mind, please describe it.
40+
41+
42+
### Describe alternatives you've considered
43+
44+
<!-- ✍️--> Have you considered any alternative solutions or workarounds?
45+

‎.github/PULL_REQUEST_TEMPLATE.md

Copy file name to clipboard
+44Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
## PR Checklist
2+
3+
Please check if your PR fulfills the following requirements:
4+
5+
- [ ] Tests for the changes have been added (for bug fixes / features)
6+
- [ ] Docs have been added / updated (for bug fixes / features)
7+
8+
9+
## PR Type
10+
11+
What kind of change does this PR introduce?
12+
13+
<!-- Please check the one that applies to this PR using "x". -->
14+
15+
- [ ] Bugfix
16+
- [ ] Feature (please, look at the "Scope of the project" section in the README.md file)
17+
- [ ] Code style update (formatting, local variables)
18+
- [ ] Refactoring (no functional changes, no api changes)
19+
- [ ] Build related changes
20+
- [ ] CI related changes
21+
- [ ] Documentation content changes
22+
- [ ] Other... Please describe:
23+
24+
25+
## What is the current behavior?
26+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
27+
28+
Issue Number: N/A
29+
30+
31+
## What is the new behavior?
32+
33+
34+
## Does this PR introduce a breaking change?
35+
36+
- [ ] Yes
37+
- [ ] No
38+
39+
40+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
41+
42+
43+
## Other information
44+

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.