Skip to content

Commit

Permalink
Add issue and PR templates (#1754)
Browse files Browse the repository at this point in the history
This helps a lot to make initial user interactions at a higher quality, so maintainers don't spend as much time asking for clarifications and so on.
  • Loading branch information
alexeagle authored Mar 12, 2021
1 parent e5b00af commit f7d034f
Show file tree
Hide file tree
Showing 3 changed files with 166 additions and 0 deletions.
77 changes: 77 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
---
name: "\U0001F41EBug report"
about: Report a bug in rules_docker
---
<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
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: -->
<!-- (Please run your build with --define=VERBOSE_LOGS=1 to gather more info for us to understand the problem.) -->
<!-- ✍️-->

</code></pre>


## 🌍 Your Environment

**Operating System:**

<pre>
<code>

</code>
</pre>

**Output of `bazel version`:**

<pre>
<code>

</code>
</pre>

**Rules_docker version:**

<pre>
<code>

</code>
</pre>

**Anything else relevant?**

45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
name: "\U0001F680Feature request"
about: Suggest a feature for rules_docker

---
<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
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?

44 changes: 44 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -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
- [ ] 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

0 comments on commit f7d034f

Please sign in to comment.