aboutsummaryrefslogtreecommitdiffstats
path: root/.github
diff options
context:
space:
mode:
authorJon Moss <me@jonathanmoss.me>2016-02-17 12:48:46 -0500
committerJon Moss <me@jonathanmoss.me>2016-02-18 14:04:00 -0500
commitcd3d89f99422af77fdc96bbd978e40685cb30179 (patch)
tree079022165671f070b482ec5805103ddcf5aa9f25 /.github
parent13c4cc3b5aea02716b7459c0da641438077f5236 (diff)
downloadrails-cd3d89f99422af77fdc96bbd978e40685cb30179.tar.gz
rails-cd3d89f99422af77fdc96bbd978e40685cb30179.tar.bz2
rails-cd3d89f99422af77fdc96bbd978e40685cb30179.zip
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]
Diffstat (limited to '.github')
-rw-r--r--.github/issue_template.md15
-rw-r--r--.github/pull_request_template.md18
2 files changed, 33 insertions, 0 deletions
diff --git a/.github/issue_template.md b/.github/issue_template.md
new file mode 100644
index 0000000000..93f328a46e
--- /dev/null
+++ b/.github/issue_template.md
@@ -0,0 +1,15 @@
+### Steps to reproduce
+
+(Guidelines for creating a bug report are [available
+here](http://guides.rubyonrails.org/contributing_to_ruby_on_rails.html#creating-a-bug-report)
+
+### Expected behavior
+Tell us what should happen
+
+### Actual behavior
+Tell us what happens instead
+
+### System configuration
+**Rails version**:
+
+**Ruby version**:
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000000..1ee3601c9e
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,18 @@
+### Summary
+
+Provide a general description of the code changes in your pull
+request... were there any bugs you had fixed? If so, mention them. If
+these bugs have open GitHub issues, be sure to tag them here as well,
+to keep the conversation linked together.
+
+### Other Information
+
+If there's anything else that's important and relevant to your pull
+request, mention that information here. This could include
+benchmarks, or other information.
+
+Finally, if your pull request affects documentation or any non-code
+changes, guidelines for those changes are [available
+here](http://guides.rubyonrails.org/contribution_to_ruby_on_rails.html#contributing-to-the-rails-documentation)
+
+Thanks for contributing to Rails!