rails--rails/.github/issue_template.md

### Steps to reproduce
<!-- (Guidelines for creating a bug report are [available
here](https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#creating-a-bug-report)) -->

<!-- Paste your executable test case created from one of the scripts found [here](https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#create-an-executable-test-case) below: -->
```ruby
# Your reproduction script goes here
```

### Expected behavior
<!-- Tell us what should happen -->

### Actual behavior
<!-- Tell us what happens instead -->

### System configuration
**Rails version**:

**Ruby version**:
Add `issue_template.md` and `pull_request_template.md` This appears to be a new feature of GitHub. See these links for more details: - https://github.com/dear-github/dear-github/issues/125 - https://github.com/owncloud/core/issues/new - https://github.com/blog/2111-issue-and-pull-request-templates [ci skip] 2016-02-17 12:48:46 -05:00			`### Steps to reproduce`
Add comments to markdown templates 2018-11-18 15:37:53 -05:00			`<!-- (Guidelines for creating a bug report are [available`
Updated links from http to https in guides, docs, etc 2019-03-08 06:36:16 -05:00			`here](https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#creating-a-bug-report)) -->`
Add `issue_template.md` and `pull_request_template.md` This appears to be a new feature of GitHub. See these links for more details: - https://github.com/dear-github/dear-github/issues/125 - https://github.com/owncloud/core/issues/new - https://github.com/blog/2111-issue-and-pull-request-templates [ci skip] 2016-02-17 12:48:46 -05:00
[ci skip] Mention executable test cases in issue template A lot of bug reports have useful reproduction steps that could be a reproduction script, but they seem to have either not found the reproduction script template or didn't read the 'contributing to rails' page at all. This links to the same page at the section that includes the reproduction scripts with a stronger call to action making it clear that they need a reproduction script. 2021-06-01 12:51:43 -04:00			`<!-- Paste your executable test case created from one of the scripts found [here](https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#create-an-executable-test-case) below: -->`
			```ruby
			`# Your reproduction script goes here`
			```

Add `issue_template.md` and `pull_request_template.md` This appears to be a new feature of GitHub. See these links for more details: - https://github.com/dear-github/dear-github/issues/125 - https://github.com/owncloud/core/issues/new - https://github.com/blog/2111-issue-and-pull-request-templates [ci skip] 2016-02-17 12:48:46 -05:00			`### Expected behavior`
Add comments to markdown templates 2018-11-18 15:37:53 -05:00			`<!-- Tell us what should happen -->`
Add `issue_template.md` and `pull_request_template.md` This appears to be a new feature of GitHub. See these links for more details: - https://github.com/dear-github/dear-github/issues/125 - https://github.com/owncloud/core/issues/new - https://github.com/blog/2111-issue-and-pull-request-templates [ci skip] 2016-02-17 12:48:46 -05:00
			`### Actual behavior`
Add comments to markdown templates 2018-11-18 15:37:53 -05:00			`<!-- Tell us what happens instead -->`
Add `issue_template.md` and `pull_request_template.md` This appears to be a new feature of GitHub. See these links for more details: - https://github.com/dear-github/dear-github/issues/125 - https://github.com/owncloud/core/issues/new - https://github.com/blog/2111-issue-and-pull-request-templates [ci skip] 2016-02-17 12:48:46 -05:00
			`### System configuration`
			`Rails version:`

			`Ruby version:`