This outlines how to propose a change to bigrquery. For more detailed info about contributing to this, and other tidyverse packages, please see the development contributing guide.
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).
See the internal help for
bq_test_project() for information about setting up a test project and test bucket.
The overall approach to managing the service account token used in tests is described in the gargle article Managing tokens securely.
Please note that the bigrquery project is released with a Contributor Code of Conduct. By contributing to this project you agree to abide by its terms.
for further details.