From 50a9b49e3760a2d1c595ed3425f680186feeb47f Mon Sep 17 00:00:00 2001 From: rickstaa Date: Sun, 24 Jul 2022 13:18:10 +0200 Subject: [PATCH] refactor: improve contributing guidelines lists --- CONTRIBUTING.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 29a48e4..fb2c9f2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,15 +38,11 @@ We use GitHub issues to track public bugs. Report a bug by [opening a new issue] **Great Bug Reports** tend to have: - A quick summary and/or background. - - Steps to reproduce: - Be specific! - Give sample code if you can. [My stackoverflow question](http://stackoverflow.com/q/12488905/180626) includes sample code that _anyone_ with a base R setup can run to reproduce what I was seeing. - - What you expected would happen. - - What actually happens. - - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work). People _love_ thorough bug reports. I'm not even kidding.