Skip to content

Commit 1dd790c

Browse files
committed
chore: add ISSUE_TEMPLATE
1 parent 3b12b9e commit 1dd790c

File tree

3 files changed

+78
-0
lines changed

3 files changed

+78
-0
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: waiting-for-triage
6+
assignees: ''
7+
8+
---
9+
**PLEASE READ**: If you have a support contract with Google, please create an issue in the
10+
[support console](https://cloud.google.com/support/) instead of filing on GitHub. This will ensure
11+
a timely response.
12+
13+
We'd love to accept your patches and contributions to this project. There are just a few small
14+
guidelines you need to follow before opening an issue or a PR:
15+
16+
1. Ensure the issue was not already reported.
17+
2. Open a new issue if you are unable to find an existing issue addressing your problem. Make sure
18+
to include a title and clear description, as much relevant information as possible, and a code
19+
sample or an executable test case demonstrating the expected behavior that is not occurring.
20+
3. Discuss the priority and potential solutions with the maintainers in the issue. The maintainers
21+
would review the issue and add a label "Accepting Contributions" once the issue is ready for
22+
accepting contributions.
23+
4. Open a PR only if the issue is labeled with "Accepting Contributions", ensure the PR description
24+
clearly describes the problem and solution. Note that an open PR without an issue labeled with "
25+
Accepting Contributions" will not be accepted.
26+
27+
See
28+
also [CONTRIBUTING.adoc](https://github.com/GoogleCloudPlatform/cloud-spanner-r2dbc/blob/main/CONTRIBUTING.adoc)
29+
.
30+
31+
**Describe the bug**
32+
Please provide details of the problem, including the version that you are using.
33+
34+
**Sample**
35+
If possible, please provide a test case or sample application that reproduces
36+
the problem. This makes it much easier for us to diagnose the problem and to verify that
37+
we have fixed it.

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
contact_links:
2+
- name: Google Cloud Support
3+
url: https://cloud.google.com/support/
4+
about: If you have a support contract with Google, please use the Google Cloud Support portal.
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: waiting-for-triage
6+
assignees: ''
7+
8+
---
9+
We'd love to accept your patches and contributions to this project. There are just a few small
10+
guidelines you need to follow before opening an issue or a PR:
11+
12+
1. Ensure the issue was not already reported.
13+
2. Open a new issue if you are unable to find an existing issue addressing your problem. Make sure
14+
to include a title and clear description, as much relevant information as possible, and a code
15+
sample or an executable test case demonstrating the expected behavior that is not occurring.
16+
3. Discuss the priority and potential solutions with the maintainers in the issue. The maintainers
17+
would review the issue and add a label "Accepting Contributions" once the issue is ready for
18+
accepting contributions.
19+
4. Open a PR only if the issue is labeled with "Accepting Contributions", ensure the PR description
20+
clearly describes the problem and solution. Note that an open PR without an issue labeled with "
21+
Accepting Contributions" will not be accepted.
22+
23+
See
24+
also [CONTRIBUTING.adoc](https://github.com/GoogleCloudPlatform/cloud-spanner-r2dbc/blob/main/CONTRIBUTING.adoc)
25+
.
26+
27+
**Is your feature request related to a problem? Please describe.**
28+
A clear and concise description of what the problem is and what version you are using. Ex. I'm always frustrated when [...]
29+
30+
**Describe the solution you'd like**
31+
A clear and concise description of what you want to happen.
32+
33+
**Describe alternatives you've considered**
34+
A clear and concise description of any alternative solutions or features you've considered.
35+
36+
**Additional context**
37+
Add any other context or screenshots about the feature request here.

0 commit comments

Comments
 (0)