This outlines how to propose a change to nullranges. (Template copied from tidyverse contribution guide).
You can fix typos, spelling mistakes, or grammatical errors in the documentation directly using the GitHub web interface, as long as the changes are made in the source file. This generally means you’ll need to edit roxygen2 comments in an
.R, not a
.Rd file. You can find the
.R file that generates the
.Rd by reading the comment in the first line.
If you want to make a bigger change, it’s a good idea to first file an issue and make sure someone from the team agrees that it’s needed. If you’ve found a bug, please file an issue that illustrates the bug with a minimal reprex (this will also help you write a unit test, if needed).
The nullranges development team has a public Slack channel
#nullranges on the community-bioc Slack. We welcome questions or suggestions there as well, if you want to discuss. I will note that GitHub Issues are also useful for having a permanent record, and for tracking bugs/suggestions.
Fork the package and clone onto your computer. If you haven’t done this before, we recommend using
usethis::create_from_github("nullranges/nullranges", fork = TRUE).
Install all development dependences with
devtools::install_dev_deps(), and then make sure the package passes R CMD check by running
devtools::check(). If R CMD check doesn’t pass cleanly, it’s a good idea to ask for help before continuing.
Create a Git branch for your pull request (PR). We recommend using
Make your changes, commit to git, and then create a PR by running
usethis::pr_push(), and following the prompts in your browser. The title of your PR should briefly describe the change. The body of your PR should contain
For user-facing changes, add a bullet to the top of
NEWS.md (i.e. just below the first header). Follow the style described in https://style.tidyverse.org/news.html.
Please note that the nullranges project is released with a Contributor Code of Conduct. By contributing to this project you agree to abide by its terms.