Contributing to VBC

Thanks for taking the time to contribute! Contributions of all kinds are welcome — bug reports, feature requests, documentation improvements, and code.

Reporting bugs and requesting features

Please open an issue at https://github.com/henrifnk/VBC/issues. For a bug report, a minimal reproducible example (a small script and, where possible, a small data subset) is the single most helpful thing you can provide, together with the output of sessionInfo().

Contributing code

1. Fork the repository and create a branch off main.
2. Make your change. Please keep the coding style consistent with the existing code and document exported functions with roxygen2.
3. Add or update tests under tests/testthat/ and make sure devtools::check() passes cleanly.
4. Update NEWS.md with a short entry describing your change.
5. Open a pull request describing what the change does and why.

Getting help

For usage questions rather than bugs, please open an issue with the “question” label. See also the package vignette and the documentation site at https://henrifnk.github.io/VBC/.

Code of Conduct

By participating in this project you agree to abide by its Code of Conduct.