Project Status: Active – The project has reached a stable, usable state and is being activelydeveloped Codecov test coverage Total Downloads CRAN status license AppVeyor build status R build status status

Thank you for taking the time to contribute to the development of serp. You could find the following guidelines useful in making your contributions.

Before you start:

  • It is important to have a valid GitHub account.
  • Trivial changes to comments or documentation do not require creating a new issue.

Did you find a bug?

  • Make sure the bug was not already reported in the Github Issues.
  • Open an issue and clearly describe the issue with as much information as possible. A code sample or an executable test case are recommended.

Did you plan to write a patch that fixes a bug?

  • Open an issue and clearly describes the problem and discuss how your solution will affect serp.
  • Fork the repository on GitHub to work on the patch.
  • Get in touch with the maintainer to refine and prioritize your issue.

Making changes and Pull requests

  • Start your work on your fork of the repository. If you haven’t done this before, try using usethis::create_from_github("ejikeugba/serp", 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().
  • Create a Git branch for your pull request (PR). You may want to use usethis::pr_init("brief-description-of-change").
  • Check for unnecessary whitespace with git diff --check and format code.
  • Commit messages should be descriptive, mentioning what was changed and why, and also reference the relevant issue number.
  • Ensure to add the necessary tests for your changes (testthat preferably).
  • Run all the tests to assure nothing else was accidentally broken, also keep an eye on the test coverage metric.
  • Commit to git, and then create a PR by running usethis::pr_push(), and following the prompts in your browser

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.