Small typos or grammatical errors in documentation may be edited directly using the GitHub web interface, so long as the changes are made in the source file.
Before you make a substantial pull request, you should always file an issue and make sure someone from the team agrees that it’s a problem. If you’ve found a bug, create an associated issue and illustrate the bug with a minimal reprex.
READMEshould contain badges for any continuous integration services used by the package.
NEWS.mdbelow the current development version header describing the changes made followed by your GitHub username, and links to relevant issue(s)/PR(s).
In order to check your contribution passes all tests, you will needt be able to run the full test suite. Instructions for how to do this can be found here.
Alternatively, you can use the package’s CI with travis, to see if the test suite has passed. This test suite uses the encrypted “rdhs.json” config within the package root to download datasets. The datasets that are available to download with this config can be viewed within the “available_test_suite_datasets.csv”.
If your contributions need access to a dataset that is not available, e.g. a new dataset that affects the flat file parsers, then open a PR and they will be requested from the DHS website.
Email the person listed as maintainer in the
DESCRIPTION file of this repo.
Though note that private discussions over email don’t help others - of course email is totally warranted if it’s a sensitive problem of any kind.
This contributing guide is adapted from the tidyverse contributing guide available at https://raw.githubusercontent.com/r-lib/usethis/master/inst/templates/tidy-contributing.md