.github/SUPPORT.md

In tidyverse/reprex: Prepare Reproducible Example Code via the Clipboard

Getting help with reprex

Thanks for using reprex. Before filing an issue, there are a few places to explore and pieces to put together to make the process as smooth as possible.

Start by making a minimal reproducible example using the reprex package. OK, that's funny, because this is the very package we're talking about! Do your best to provide your input, the reprex() call, the expected result, and the actual result. Make it easy to reproduce your problem. For additional reprex pointers, check out the Get help! section of the tidyverse site.

Armed with your reprex, the next step is to figure out where to ask.

• If it's a question: start with community.rstudio.com, and/or StackOverflow. There are more people there to answer questions.
• If it's a bug: you're in the right place, file an issue.
• If you're not sure: let the community help you figure it out! If your problem is a bug or a feature request, you can easily return here and report it.

Before opening a new issue, be sure to search issues and pull requests to make sure the bug hasn't been reported and/or already fixed in the development version. By default, the search will be pre-populated with is:issue is:open. You can edit the qualifiers (e.g. is:pr, is:closed) as needed. For example, you'd simply remove is:open to search all issues in the repo, open or closed.

If you are in the right place, and need to file an issue, please review the "File issues" paragraph from the tidyverse contributing guidelines.

Thanks for your help!

tidyverse/reprex documentation built on Jan. 27, 2024, 5:55 p.m.