CONTRIBUTING.md
In nathaneastwood/euler: Solve Project Euler Problems
Contributing
Contributions via GitHub pull requests are gladly accepted from their original author. By participating in this project, you agree to abide by the thoughtbot code of conduct.
Licensing
Along with any pull requests, please state that the contribution is your original work and that you license the work to the project under the project's open source license. Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project's open source license and warrant that you have the legal authority to do so.
R Coding Standards
We follow the style guide maintained within the tidyverse. This is tested using the lintr package; you can automatically conform your code to these standards using the styler package.
git Commit Standards
We follow the commit message style guide maintained within the angular.js project.
The start of commit messages must be one of the following:
- feat: A new feature
- fix: A bug fix
- doc: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space,
formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug or adds a feature
- perf: A code change that improves performance
- test: Adding missing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Do not capitalise the first letter.
nathaneastwood/euler documentation built on June 18, 2019, 11:20 a.m.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Contributing
Contributions via GitHub pull requests are gladly accepted from their original author. By participating in this project, you agree to abide by the thoughtbot code of conduct.
Licensing
Along with any pull requests, please state that the contribution is your original work and that you license the work to the project under the project's open source license. Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project's open source license and warrant that you have the legal authority to do so.
R Coding Standards
We follow the style guide maintained within the tidyverse. This is tested using the lintr package; you can automatically conform your code to these standards using the styler package.
git Commit Standards
We follow the commit message style guide maintained within the angular.js project.
The start of commit messages must be one of the following:
- feat: A new feature
- fix: A bug fix
- doc: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug or adds a feature
- perf: A code change that improves performance
- test: Adding missing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Do not capitalise the first letter.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.