Contributing guide

Code of Conduct

Anyone getting involved in this package agrees to our Code of Conduct. If someone is breaking the Will Wheaton rule aka Don't be a dick, or breaking the Code of Conduct, please let me know at steph@itsalocke.com or keybase.io/stephlocke.

Bug reports

When you file a bug report, please spend some time making it easy for us to follow and reproduce. The more time you spend on making the bug report coherent, the more time we can dedicate to investigate the bug as opposed to the bug report. We recommend using reprex when providing minimal examples.

If you need a secure way to communicate with the maintainer of this package, message her via her Keybase account.


Got an idea for how we can improve the package? Awesome stuff!

Please raise it in the issue tracker with some succinct information on expected behaviour of the enhancement and why you think it'll improve the package.

Package development

We really want people to contribute to the package. A great way to start doing this is to look at the help wanted issues and/or contribute an example.


We're relatively loose on coding conventions.

New features should be accompanied by new unit tests. We're glad to help with that if you're new to testing!

lockedata/cransays documentation built on Oct. 10, 2021, 10:02 a.m.