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 have found a bug, create an associated issue and illustrate the bug with a minimal reprex.
-
We recommend that you create a Git branch for each pull request (PR).
-
Look at the Github Actions and AppVeyor build status before and after making changes.
-
We recommend the tidyverse style guide. You can use the styler package to apply these styles, but please don't restyle code that has nothing to do with your PR.
- For user-facing changes, add a bullet to the top of
NEWS.md
below the current development version header describing the changes made followed by your GitHub username, and links to relevant issue(s)/PR(s).
Please note that the HeliconiaSurveys
project is released with a
Contributor Code of Conduct. By contributing to this
project you agree to abide by its terms.
You may write to Emilio M. Bruna at embruna@ufl.edu.
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