📃 Liquid tag for displaying GitHub Gists in Jekyll sites.
Ruby Shell
Failed to load latest commit information.
lib Don't ask .empty? until it's a String. Dec 19, 2016
spec whitespace Dec 1, 2015
.gitignore Initial import. Jun 1, 2014
.rspec Add tests for the gist tag. Jun 1, 2014
.travis.yml Test against Jekyll 3 Aug 31, 2015
Gemfile Test against Jekyll 3 Aug 31, 2015
History.markdown Update history to reflect merge of #38 [ci skip] Dec 19, 2016
LICENSE.txt Initial import. Jun 1, 2014
Rakefile Remove a empty line in Rakefile Feb 8, 2016
jekyll-gist.gemspec use octokit to fetch gists when token present Nov 30, 2015



Liquid tag for displaying GitHub Gists in Jekyll sites: {% gist %}.

Build Status


Add this line to your application's Gemfile:

gem 'jekyll-gist'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jekyll-gist

Finally, add the following to your site's _config.yml:

  - jekyll-gist


Use the tag as follows in your Jekyll pages, posts and collections:

{% gist parkr/c08ee0f2726fd0e3909d %}

This will create the associated script tag:

<script src="https://gist.github.com/parkr/c08ee0f2726fd0e3909d.js"> </script>

You may optionally specify a filename after the gist_id:

{% gist parkr/c08ee0f2726fd0e3909d test.md %}

This will produce the correct URL to show just the specified file in your post rather than the entire Gist.

Pro-tip: If you provide a personal access token with Gist scope, as the environmental variable JEKYLL_GITHUB_TOKEN, Jekyll Gist will use the Gist API to speed up site generation.

Disabling noscript support

By default, Jekyll Gist will make an HTTP call per Gist to retrieve the raw content of the Gist. This information is used to propagate noscript tags for search engines and browsers without Javascript support. If you'd like to disable this feature, for example, to speed up builds locally, simply add the following to your site's _config.yml:

  noscript: false


  1. Fork it ( https://github.com/jekyll/jekyll-gist/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request