Contributions to anyflights, whether in the form of bug fixes, issue reports, new code or documentation improvements are encouraged and welcome. Of particular interest is increasing unit testing coverage, checking supplied arguments more thoroughly, and getting generated data packages to pass R CMD CHECK in a variety of edge cases.

Maximal goofiness in commit messages and description of issues/PRs, including but not limited to emojis, excessive punctuation (!!!), or ridiculous capitalization is encouraged but not required.

Please use snake case (such as get_flights) for function names. Besides that, in general follow the tidyverse style guide for R.

Code of Conduct

As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion.

Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned to this Code of Conduct.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.

This Code of Conduct is adapted from the Contributor Covenant, version 1.0.0, available at