-
-
Notifications
You must be signed in to change notification settings - Fork 276
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add issue templates for bug reports and feature requests
I think this will minimize the questions.
- Loading branch information
Showing
2 changed files
with
68 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
--- | ||
name: Bug Report | ||
about: Report an issue with RuboCop RSpec you've discovered. | ||
--- | ||
|
||
*Be clear, concise and precise in your description of the problem. | ||
Open an issue with a descriptive title and a summary in grammatically correct, | ||
complete sentences.* | ||
|
||
*Use the template below when reporting bugs. Please, make sure that | ||
you're running the latest stable RuboCop RSpec and that the problem you're reporting | ||
hasn't been reported (and potentially fixed) already.* | ||
|
||
*Before filing the ticket you should replace all text above the horizontal | ||
rule with your own words.* | ||
|
||
*In the case of false positive or false negative, please add the | ||
corresponding cop name.* | ||
|
||
______________________________________________________________________ | ||
|
||
## Expected behavior | ||
|
||
Describe here how you expected RuboCop RSpec to behave in this particular situation. | ||
|
||
## Actual behavior | ||
|
||
Describe here what actually happened. | ||
Please use `rubocop --debug` when pasting rubocop output as it contains additional information. | ||
|
||
## Steps to reproduce the problem | ||
|
||
This is extremely important! Providing us with a reliable way to reproduce | ||
a problem will expedite its solution. | ||
|
||
## RuboCop RSpec version | ||
|
||
Include the output of `rubocop -V` or `bundle exec rubocop -V` if using Bundler. | ||
If you see extension cop versions (e.g. `rubocop-performance`, `rubocop-rake`, and others) | ||
output by `rubocop -V`, include them as well. Here's an example: | ||
|
||
```shell | ||
$ [bundle exec] rubocop -V | ||
1.67.0 (using Parser 3.3.5.0, rubocop-ast 1.32.3, analyzing as Ruby 2.7, running on ruby 3.4.0) [arm64-darwin23] | ||
- rubocop-performance 1.22.1 | ||
- rubocop-rake 0.6.0 | ||
- rubocop-rspec 3.1.0 | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
name: Feature Request | ||
about: Suggest new RuboCop RSpec features or improvements to existing features. | ||
--- | ||
|
||
## Is your feature request related to a problem? Please describe. | ||
|
||
A clear and concise description of what the problem is. Ex. I'm always frustrated when \[...\] | ||
|
||
## Describe the solution you'd like | ||
|
||
A clear and concise description of what you want to happen. | ||
|
||
## Describe alternatives you've considered | ||
|
||
A clear and concise description of any alternative solutions or features you've considered. | ||
|
||
## Additional context | ||
|
||
Add any other context or screenshots about the feature request here. |