Skip to content

Commit 7d42e08

Browse files
Kieran O'GradyJonRowe
authored andcommitted
Provide instructions in issue templates
Indicate the preferred process of requesting users to first discuss feature requests in the project google group.
1 parent f5f27cd commit 7d42e08

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -9,16 +9,8 @@ assignees: ''
99

1010
<!--
1111
12-
Hi there! Here's a few pointers to help us help you with your issue as quickly
13-
as possible.
14-
15-
We prefer that the RSpec Rails issue tracker be mainly used for bug reports.
16-
Feature requests or general requests for help should go to our google group:
17-
[email protected]. We use that as our primary location for higher level
18-
RSpec discussions.
19-
20-
If you are filing a bug report, there's a few steps it'd be super if you could
21-
follow. If you can't do all of these, don't worry, but if you can it'll help us
12+
Below are a few steps it'd be super if you could follow.
13+
If you can't do all of these, don't worry, but if you can it'll help us
2214
resolve your bug faster!
2315
2416
-->

.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,14 @@ assignees: ''
77

88
---
99

10+
<!--
11+
12+
Feature requests or general requests for help should first go to our google group:
13+
[email protected]. We use that as our primary location for higher level
14+
RSpec discussions.
15+
16+
-->
17+
1018
**Is your feature request related to a problem? Please describe.**
1119
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
1220

0 commit comments

Comments
 (0)