Skip to content

Commit d96335f

Browse files
committed
Update issue templates and add pull request template
1 parent a67eebb commit d96335f

File tree

3 files changed

+58
-0
lines changed

3 files changed

+58
-0
lines changed

.github/issue_template.md renamed to .github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
**It is strongly preferable to create an issue in [Apache JIRA Cassandra project](https://issues.apache.org/jira/projects/CASSANDRA/issues/).**
11+
112
Please answer these questions before submitting your issue. Thanks!
213

314
### What version of Cassandra are you using?
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**It is strongly preferable to create an issue in [Apache JIRA Cassandra project](https://issues.apache.org/jira/projects/CASSANDRA/issues/).**
11+
12+
Please answer these questions before submitting your issue. Thanks!
13+
14+
**Is your feature request related to a problem? Please describe.**
15+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
16+
17+
**Describe the solution you'd like**
18+
A clear and concise description of what you want to happen.
19+
20+
**Describe alternatives you've considered**
21+
A clear and concise description of any alternative solutions or features you've considered.
22+
23+
**Additional context**
24+
Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
Thanks for sending a pull request! Here are some tips if you're new here:
2+
3+
* Reflect JIRA ticket number in the pull request title
4+
* Be sure to keep the PR description updated to reflect all changes.
5+
* Write your PR title to summarize what this PR proposes.
6+
* If possible, provide a concise example to reproduce the issue for a faster review.
7+
8+
Commit messages should follow the following format:
9+
10+
```
11+
<One sentence description, usually Jira title or CHANGES.txt summary>
12+
13+
<Optional lengthier description (context on patch)>
14+
15+
patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####
16+
17+
Co-authored-by: Name1 <email1>
18+
Co-authored-by: Name2 <email2>
19+
20+
```
21+
22+
The [Cassandra Jira](https://issues.apache.org/jira/projects/CASSANDRA/issues/)
23+

0 commit comments

Comments
 (0)