发现错误或贡献翻译

Contributing

Hi there! Interested in contributing to Jekyll? We’d love your help. Jekyll is an open source project, built one contribution at a time by users like you.

Where to get help or report a problem

If you have a question about using Jekyll, start a discussion on Jekyll Talk.
If you think you’ve found a bug within a Jekyll plugin, open an issue in that plugin’s repository.
If you think you’ve found a bug within Jekyll itself, open an issue.
More resources are listed on our Help page.

Ways to contribute

Whether you’re a developer, a designer, or just a Jekyll devotee, there are lots of ways to contribute. Here’s a few ideas:

Install Jekyll on your computer and kick the tires. Does it work? Does it do what you’d expect? If not, open an issue and let us know.
Comment on some of the project’s open issues. Have you experienced the same problem? Know a work around? Do you have a suggestion for how the feature could be better?
Read through the documentation, and click the “improve this page” button, any time you see something confusing, or have a suggestion for something that could be improved.
Browse through the Jekyll discussion forum, and lend a hand answering questions. There’s a good chance you’ve already experienced what another user is experiencing.
Find an open issue (especially those labeled help-wanted), and submit a proposed fix. If it’s your first pull request, we promise we won’t bite, and are glad to answer any questions.
Help evaluate open pull requests, by testing the changes locally and reviewing what’s proposed.

Submitting a pull request

Pull requests generally

The smaller the proposed change, the better. If you’d like to propose two unrelated changes, submit two pull requests.
The more information, the better. Make judicious use of the pull request body. Describe what changes were made, why you made them, and what impact they will have for users.
Pull request are easy and fun. If this is your first pull request, it may help to understand GitHub Flow.
If you’re submitting a code contribution, be sure to read the code contributions section below.

Submitting a pull request via github.com

Many small changes can be made entirely through the github.com web interface.

Navigate to the file within jekyll/jekyll that you’d like to edit.
Click the pencil icon in the top right corner to edit the file
Make your proposed changes
Click “Propose file change”
Click “Create pull request”
Add a descriptive title and detailed description for your proposed change. The more information the better.
Click “Create pull request”

That’s it! You’ll be automatically subscribed to receive updates as others review your proposed change and provide feedback.

Submitting a pull request via Git command line

Fork the project by clicking “Fork” in the top right corner of jekyll/jekyll.
Clone the repository locally git clone https://github.com/<you-username>/jekyll.
Create a new, descriptively named branch to contain your change ( git checkout -b my-awesome-feature ).
Hack away, add tests. Not necessarily in that order.
Make sure everything still passes by running script/cibuild (see the tests section below)
Push the branch up ( git push origin my-awesome-feature ).
Create a pull request by visiting https://github.com/<your-username>/jekyll and following the instructions at the top of the screen.

Proposing updates to the documentation

We want the Jekyll documentation to be the best it can be. We’ve open-sourced our docs and we welcome any pull requests if you find it lacking.

How to submit changes

You can find the documentation for jekyllrb.com in the site directory. See the section above, submitting a pull request for information on how to propose a change.

One gotcha, all pull requests should be directed at the master branch (the default branch).

Adding plugins

If you want to add your plugin to the list of plugins, please submit a pull request modifying the plugins page source file by adding a link to your plugin under the proper subheading depending upon its type.

Code Contributions

Interesting in submitting a pull request? Awesome. Read on. There’s a few common gotchas that we’d love to help you avoid.

Tests and documentation

Any time you propose a code change, you should also include updates to the documentation and tests within the same pull request.

Documentation

If your contribution changes any Jekyll behavior, make sure to update the documentation. Documentation lives in the site/_docs folder (spoiler alert: it’s a Jekyll site!). If the docs are missing information, please feel free to add it in. Great docs make a great project. Include changes to the documentation within your pull request, and once merged, jekyllrb.com will be updated.

Tests

If you’re creating a small fix or patch to an existing feature, a simple test is more than enough. You can usually copy/paste from an existing example in the tests folder, but if you need you can find out about our tests suites Shoulda and RSpec-Mocks.
If it’s a brand new feature, create a new Cucumber feature, reusing existing steps where appropriate.

Code contributions generally

Jekyll uses the Rubocop static analyzer to ensure that contributions follow the GitHub Ruby Styleguide. 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).

Running tests locally

Test Dependencies

To run the test suite and build the gem you’ll need to install Jekyll’s dependencies by running the following command:

$ script/bootstrap

Before you make any changes, run the tests and make sure that they pass (to confirm your environment is configured properly):

$ script/cibuild

If you are only updating a file in test/, you can use the command:

$ script/test test/blah_test.rb

If you are only updating a .feature file, you can use the command:

$ script/cucumber features/blah.feature

Both script/test and script/cucumber can be run without arguments to run its entire respective suite.

A thank you

Thanks! Hacking on Jekyll should be fun. If you find any of this hard to figure out, let us know so we can improve our process or documentation!