dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Backport #5138 to .github/CONTRIBUTING.markdown

This commit is contained in:
Parker Moore 2016-07-26 09:54:33 -07:00
parent dbf312eec0
commit 55317817d1
No known key found for this signature in database
GPG Key ID: 193CDEBA72063C58
2 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/CONTRIBUTING.markdown vendored
View File

@ -90,7 +90,7 @@ If your contribution changes any Jekyll behavior, make sure to update the docume
### Code contributions generally ### Code contributions generally
* Jekyll follows the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby). * Jekyll uses the [Rubocop](https://github.com/bbatsov/rubocop) static analyzer to ensure that contributions follow the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby). Please check your code using `script/fmt` and resolve any errors before pushing your branch.
* Don't bump the Gem version in your pull request (if you don't know what that means, you probably didn't). * Don't bump the Gem version in your pull request (if you don't know what that means, you probably didn't).

5
site/_docs/contributing.md
View File

@ -95,10 +95,7 @@ If your contribution changes any Jekyll behavior, make sure to update the docume
### Code contributions generally ### Code contributions generally
* Jekyll uses the [Rubocop](https://github.com/bbatsov/rubocop) static * Jekyll uses the [Rubocop](https://github.com/bbatsov/rubocop) static analyzer to ensure that contributions follow the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby). Please check your code using `script/fmt` and resolve any errors before pushing your branch.
analyzer to ensure that contributions follow the
[GitHub Ruby Styleguide](https://github.com/styleguide/ruby). Please check your
code using `script/fmt` and resolve any errors before pushing your branch.
* Don't bump the Gem version in your pull request (if you don't know what that means, you probably didn't). * Don't bump the Gem version in your pull request (if you don't know what that means, you probably didn't).