Whitespace cleanup.
This commit is contained in:
parent
5e74610755
commit
5ca080ac6f
|
@ -1,8 +1,8 @@
|
|||
<!--
|
||||
Hi! Thanks for considering to file a bug with Jekyll. Please take the time to
|
||||
Hi! Thanks for considering to file a bug with Jekyll. Please take the time to
|
||||
answer the basic questions. You can convert `[ ]` into `[x]` to check boxes (or submit
|
||||
and check.) If there is no need for certain fields like output and redirection, please delete
|
||||
those headers before submitting. We know not all tickets require those steps.
|
||||
those headers before submitting. We know not all tickets require those steps.
|
||||
Otherwise, please try to be as detailed as possible.
|
||||
|
||||
If you are unsure this is a bug in Jekyll, or this is a bug caused
|
||||
|
|
|
@ -105,7 +105,7 @@
|
|||
* Add timings for each scenario in cucumber & print worst offenders (#4908)
|
||||
* rubocop: jekyll/lib/filters.rb (#4993)
|
||||
* Fix rubocop offenses in exe/jekyll (#5017)
|
||||
* Rubocop: lib/jekyll/command.rb (#5018)
|
||||
* Rubocop: lib/jekyll/command.rb (#5018)
|
||||
* rubocop: lib/jekyll/static_file.rb (#5019)
|
||||
* rubocop: lib/jekyll/utils.rb (#5026)
|
||||
* rubocop: lib/jekyll/regenerator.rb (#5025)
|
||||
|
|
|
@ -48,4 +48,4 @@ Is what they wanted to get something we want to happen? Sometimes a bug report i
|
|||
|
||||
### Staleness and automatic closure
|
||||
|
||||
@jekyllbot will automatically mark issues as `stale` if no activity occurs for at least one month. @jekyllbot leaves a comment asking for information about reproducibility in current versions. If no one responds after another month, the issue is automatically closed.
|
||||
@jekyllbot will automatically mark issues as `stale` if no activity occurs for at least one month. @jekyllbot leaves a comment asking for information about reproducibility in current versions. If no one responds after another month, the issue is automatically closed.
|
||||
|
|
|
@ -146,7 +146,7 @@ module Jekyll
|
|||
#
|
||||
# string - the filename or title to slugify
|
||||
# mode - how string is slugified
|
||||
# cased - whether to replace all uppercase letters with their
|
||||
# cased - whether to replace all uppercase letters with their
|
||||
# lowercase counterparts
|
||||
#
|
||||
# When mode is "none", return the given string.
|
||||
|
|
|
@ -6,7 +6,7 @@ set -e
|
|||
|
||||
if [[ -z "$TEST_SUITE" ]]
|
||||
then
|
||||
script/test ci
|
||||
script/test ci
|
||||
script/cucumber
|
||||
elif [[ -x "script/$TEST_SUITE" ]]
|
||||
then
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
set -e
|
||||
|
||||
function msg {
|
||||
printf "\e[0;37m==> $1\e[0m\n"
|
||||
printf "\e[0;37m==> $1\e[0m\n"
|
||||
}
|
||||
|
||||
INGORE_HREFS=$(ruby -e 'puts %w{
|
||||
|
|
|
@ -436,7 +436,7 @@ Using [YAML Front Matter](../frontmatter/) is one way that you can specify confi
|
|||
|
||||
Often times, you will find that you are repeating a lot of configuration options. Setting the same layout in each file, adding the same category - or categories - to a post, etc. You can even add custom variables like author names, which might be the same for the majority of posts on your blog.
|
||||
|
||||
Instead of repeating this configuration each time you create a new post or page, Jekyll provides a way to set these defaults in the site configuration. To do this, you can specify site-wide defaults using the `defaults` key in the `_config.yml` file in your project's root directory.
|
||||
Instead of repeating this configuration each time you create a new post or page, Jekyll provides a way to set these defaults in the site configuration. To do this, you can specify site-wide defaults using the `defaults` key in the `_config.yml` file in your project's root directory.
|
||||
|
||||
The `defaults` key holds an array of scope/values pairs that define what defaults should be set for a particular file path, and optionally, a file type in that path.
|
||||
|
||||
|
|
|
@ -156,7 +156,7 @@ your host uses a different port than the default (e.g, HostGator)
|
|||
Using this setup, you might run the following command:
|
||||
|
||||
{% highlight shell %}
|
||||
rsync -crvz --rsh='ssh -p2222' --delete-after --delete-excluded _site/ hostuser@example.org:
|
||||
rsync -crvz --rsh='ssh -p2222' --delete-after --delete-excluded _site/ hostuser@example.org:
|
||||
{% endhighlight %}
|
||||
|
||||
Don't forget the column `:` after server name!
|
||||
|
@ -178,7 +178,7 @@ Alternatively, you can use an `rsync-exclude.txt` file to control which files wi
|
|||
|
||||
#### Done!
|
||||
|
||||
Now it's possible to publish your website simply by running the `deploy`
|
||||
Now it's possible to publish your website simply by running the `deploy`
|
||||
script. If your SSH certificate is [passphrase-protected](https://martin.kleppmann.com/2013/05/24/improving-security-of-ssh-private-keys.html), you will be asked to enter it when the
|
||||
script executes.
|
||||
|
||||
|
|
|
@ -125,6 +125,6 @@ date: 2016-02-06 19:32:10 -0800
|
|||
|
||||
### My categories have stopped working!
|
||||
|
||||
If you organized your categories as `/_posts/code/2008-12-24-closures.md`, you will need to restructure your directories to put the categories _above_ the `_posts` directories, as follows: `/code/_posts/2008-12-24-closures.md`.
|
||||
If you organized your categories as `/_posts/code/2008-12-24-closures.md`, you will need to restructure your directories to put the categories _above_ the `_posts` directories, as follows: `/code/_posts/2008-12-24-closures.md`.
|
||||
|
||||
_Did we miss something? Please click "Improve this page" above and add a section. Thanks!_
|
||||
|
|
|
@ -12,13 +12,13 @@ permalink: /community/
|
|||
|
||||
{{ featured.topic }} - [{{ featured.speaker }}](https://twitter.com/{{ featured.twitter_handle }})
|
||||
<div class="videoWrapper">
|
||||
<iframe width="420" height="315" src="https://www.youtube.com/embed/{{ featured.youtube_id }}" frameborder="0" allowfullscreen></iframe>
|
||||
<iframe width="420" height="315" src="https://www.youtube.com/embed/{{ featured.youtube_id }}" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
{% assign talks = site.data.jekyllconf-talks | group_by: 'year' %}
|
||||
{% for year in talks reversed %}
|
||||
## {{ year.name }}
|
||||
{% for talk in year.items %}
|
||||
{% for talk in year.items %}
|
||||
* [{{ talk.topic }}](https://youtu.be/{{ talk.youtube_id }}) - [{{ talk.speaker }}](https://twitter.com/{{ talk.twitter_handle }})
|
||||
{% endfor %}
|
||||
{% endfor %}
|
||||
{% endfor %}
|
||||
|
|
Loading…
Reference in New Issue