This outlines how to propose a change to nullranges. (Template copied from tidyverse contribution guide).

Fixing typos

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.

Bigger changes

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).

Slack channel

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.

Pull request process

Code style

  • We use roxygen2 for documentation.

  • We use testthat for unit tests. Contributions with test cases included are easier to accept.

Code of Conduct

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.