Skip to contents

This outlines how to propose a change to {a11ytables}.

Fixing typos

  • You can fix typos, spelling mistakes, or grammatical errors in the documentation directly using the GitHub web interface, as long as the changes are made in the source file.
  • This generally means you’ll need to edit roxygen2 comments in an .R, not a .Rd file.
  • You can find the .R file that generates the .Rd by reading the comment in the first line.

Bigger changes

Pull request process

  • Fork the package and clone onto your computer.
  • Install all development dependencies with devtools::install_dev_deps(), and then make sure the package passes R CMD check by running devtools::check(). If R CMD check doesn’t pass cleanly, it’s a good idea to ask for help before continuing.
  • Create a Git branch for your pull request (PR). The new branch name should start with your initials, e.g. ‘xy-fix-bug’.
  • Make your changes, commit to git, and then create a PR. The title of your PR should briefly describe the change. The body of your PR should contain Fixes #issue-number.
  • For user-facing changes, add a bullet to the top of (i.e. just below the first header).

Code style

  • New code should follow 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.
  • We use roxygen2 for documentation.
  • We use testthat for unit tests. Contributions with test cases included are easier to accept.

Code of Conduct

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


This document is an amended version of the tidy contributing guide generated by usethis::use_tidy_contributing().