jekyll-docs 3.8.5 → 3.9.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (143) hide show
  1. checksums.yaml +4 -4
  2. data/site/404.html +5 -4
  3. data/site/docs/assets/index.html +22 -21
  4. data/site/docs/code_of_conduct/index.html +8 -7
  5. data/site/docs/collections/index.html +44 -43
  6. data/site/docs/conduct/index.html +8 -7
  7. data/site/docs/configuration/index.html +68 -67
  8. data/site/docs/continuous-integration/buddyworks/index.html +10 -9
  9. data/site/docs/continuous-integration/circleci/index.html +13 -12
  10. data/site/docs/continuous-integration/index.html +8 -7
  11. data/site/docs/continuous-integration/travis-ci/index.html +32 -31
  12. data/site/docs/contributing/index.html +34 -33
  13. data/site/docs/datafiles/index.html +24 -23
  14. data/site/docs/deployment-methods/index.html +30 -29
  15. data/site/docs/drafts/index.html +11 -10
  16. data/site/docs/extras/index.html +9 -8
  17. data/site/docs/frontmatter/index.html +8 -7
  18. data/site/docs/github-pages/index.html +19 -18
  19. data/site/docs/history/index.html +674 -645
  20. data/site/docs/home/index.html +8 -7
  21. data/site/docs/includes/index.html +44 -43
  22. data/site/docs/installation/index.html +16 -15
  23. data/site/docs/maintaining/affinity-team-captain/index.html +11 -10
  24. data/site/docs/maintaining/avoiding-burnout/index.html +8 -7
  25. data/site/docs/maintaining/becoming-a-maintainer/index.html +9 -8
  26. data/site/docs/maintaining/index.html +8 -7
  27. data/site/docs/maintaining/merging-a-pull-request/index.html +23 -22
  28. data/site/docs/maintaining/releasing-a-new-version/index.html +19 -18
  29. data/site/docs/maintaining/reviewing-a-pull-request/index.html +10 -9
  30. data/site/docs/maintaining/special-labels/index.html +14 -13
  31. data/site/docs/maintaining/triaging-an-issue/index.html +12 -11
  32. data/site/docs/migrations/index.html +9 -8
  33. data/site/docs/pages/index.html +12 -11
  34. data/site/docs/pagination/index.html +25 -24
  35. data/site/docs/permalinks/index.html +33 -32
  36. data/site/docs/plugins/index.html +57 -56
  37. data/site/docs/posts/index.html +37 -36
  38. data/site/docs/quickstart/index.html +18 -17
  39. data/site/docs/resources/index.html +9 -8
  40. data/site/docs/sites/index.html +8 -7
  41. data/site/docs/static-files/index.html +14 -13
  42. data/site/docs/structure/index.html +8 -7
  43. data/site/docs/support/index.html +9 -8
  44. data/site/docs/templates/index.html +44 -43
  45. data/site/docs/themes/index.html +63 -62
  46. data/site/docs/troubleshooting/index.html +48 -47
  47. data/site/docs/upgrading/0-to-2/index.html +51 -50
  48. data/site/docs/upgrading/2-to-3/index.html +35 -34
  49. data/site/docs/upgrading/index.html +11 -10
  50. data/site/docs/usage/index.html +15 -14
  51. data/site/docs/variables/index.html +8 -7
  52. data/site/docs/windows/index.html +29 -28
  53. data/site/feed.xml +45 -41
  54. data/site/help/index.html +7 -6
  55. data/site/index.html +7 -6
  56. data/site/jekyllconf/index.html +9 -8
  57. data/site/latest_version.txt +1 -1
  58. data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +16 -10
  59. data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +18 -12
  60. data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +19 -13
  61. data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +20 -14
  62. data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +19 -13
  63. data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +16 -10
  64. data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +18 -12
  65. data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +18 -12
  66. data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +21 -15
  67. data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +19 -13
  68. data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +16 -10
  69. data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +25 -19
  70. data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +17 -11
  71. data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +17 -11
  72. data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +16 -10
  73. data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +18 -12
  74. data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +17 -11
  75. data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +17 -11
  76. data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +17 -11
  77. data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +20 -14
  78. data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +16 -10
  79. data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +16 -10
  80. data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +21 -15
  81. data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +18 -12
  82. data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +17 -11
  83. data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +24 -18
  84. data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +23 -17
  85. data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +22 -16
  86. data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +16 -10
  87. data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +18 -12
  88. data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +16 -10
  89. data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +16 -10
  90. data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +16 -10
  91. data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +16 -10
  92. data/site/news/2015/02/26/introducing-jekyll-talk/index.html +16 -10
  93. data/site/news/2015/10/26/jekyll-3-0-released/index.html +21 -15
  94. data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +20 -14
  95. data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +18 -12
  96. data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +21 -15
  97. data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +21 -15
  98. data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +17 -11
  99. data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +18 -12
  100. data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +16 -10
  101. data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +17 -11
  102. data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +17 -11
  103. data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +16 -10
  104. data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +22 -16
  105. data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +17 -11
  106. data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +17 -11
  107. data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +16 -10
  108. data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +20 -14
  109. data/site/news/2016/08/02/jekyll-3-2-1-released/index.html +17 -11
  110. data/site/news/2016/08/24/jekyll-admin-initial-release/index.html +16 -10
  111. data/site/news/2016/10/06/jekyll-3-3-is-here/index.html +42 -36
  112. data/site/news/2016/11/14/jekyll-3-3-1-released/index.html +17 -11
  113. data/site/news/2017/01/18/jekyll-3-4-0-released/index.html +18 -12
  114. data/site/news/2017/03/02/jekyll-3-4-1-released/index.html +17 -11
  115. data/site/news/2017/03/09/jekyll-3-4-2-released/index.html +21 -15
  116. data/site/news/2017/03/21/jekyll-3-4-3-released/index.html +26 -20
  117. data/site/news/2017/06/15/jekyll-3-5-0-released/index.html +25 -19
  118. data/site/news/2017/07/17/jekyll-3-5-1-released/index.html +18 -12
  119. data/site/news/2017/08/12/jekyll-3-5-2-released/index.html +21 -15
  120. data/site/news/2017/09/21/jekyll-3-6-0-released/index.html +17 -11
  121. data/site/news/2017/10/19/diversity-open-source/index.html +18 -12
  122. data/site/news/2017/10/21/jekyll-3-6-2-released/index.html +18 -12
  123. data/site/news/2018/01/02/jekyll-3-7-0-released/index.html +21 -15
  124. data/site/news/2018/01/25/jekyll-3-7-2-released/index.html +26 -20
  125. data/site/news/2018/02/19/meet-jekyll-s-new-lead-developer/index.html +16 -10
  126. data/site/news/2018/02/24/jekyll-3-7-3-released/index.html +22 -16
  127. data/site/news/2018/05/01/jekyll-3-8-1-released/index.html +19 -13
  128. data/site/news/2018/05/19/jekyll-3-8-2-released/index.html +17 -11
  129. data/site/news/2018/06/05/jekyll-3-8-3-released/index.html +19 -13
  130. data/site/news/2019/07/02/jekyll-3-8-6-released/index.html +623 -0
  131. data/site/news/index.html +263 -218
  132. data/site/news/releases/index.html +261 -216
  133. data/site/philosophy.html +1 -1
  134. data/site/sitemap.xml +61 -57
  135. data/site/team/index.html +7 -6
  136. data/site/tutorials/convert-site-to-jekyll/index.html +97 -96
  137. data/site/tutorials/custom-404-page/index.html +16 -15
  138. data/site/tutorials/home/index.html +10 -9
  139. data/site/tutorials/navigation/index.html +102 -101
  140. data/site/tutorials/orderofinterpretation/index.html +32 -31
  141. data/site/tutorials/using-jekyll-with-bundler/index.html +19 -18
  142. data/site/tutorials/video-walkthroughs/index.html +8 -7
  143. metadata +10 -24
@@ -3,7 +3,7 @@
3
3
  <head>
4
4
  <meta charset="UTF-8">
5
5
  <meta name="viewport" content="width=device-width,initial-scale=1">
6
- <meta name="generator" content="Jekyll v3.8.5">
6
+ <meta name="generator" content="Jekyll v3.9.0">
7
7
  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
8
8
  <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
9
9
  <link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
11
11
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
12
12
  <link rel="stylesheet" href="/css/screen.css">
13
13
  <link rel="icon" type="image/x-icon" href="/favicon.ico">
14
- <!-- Begin Jekyll SEO tag v2.5.0 -->
14
+ <!-- Begin Jekyll SEO tag v2.6.1 -->
15
15
  <title>Avoiding Burnout | Jekyll • Simple, blog-aware, static sites</title>
16
- <meta name="generator" content="Jekyll v3.8.5" />
16
+ <meta name="generator" content="Jekyll v3.9.0" />
17
17
  <meta property="og:title" content="Avoiding Burnout" />
18
18
  <meta property="og:locale" content="en_US" />
19
19
  <meta name="description" content="This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone." />
@@ -22,12 +22,13 @@
22
22
  <meta property="og:url" content="https://jekyllrb.com/docs/maintaining/avoiding-burnout/" />
23
23
  <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
24
24
  <meta property="og:type" content="article" />
25
- <meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
25
+ <meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
26
26
  <meta name="twitter:card" content="summary" />
27
+ <meta property="twitter:title" content="Avoiding Burnout" />
27
28
  <meta name="twitter:site" content="@jekyllrb" />
28
29
  <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
29
30
  <script type="application/ld+json">
30
- {"headline":"Avoiding Burnout","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/maintaining/avoiding-burnout/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/avoiding-burnout/"},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
31
+ {"url":"https://jekyllrb.com/docs/maintaining/avoiding-burnout/","headline":"Avoiding Burnout","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/avoiding-burnout/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
31
32
  <!-- End Jekyll SEO tag -->
32
33
 
33
34
  <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
72
73
  <div class="meta hide-on-mobiles">
73
74
  <ul>
74
75
  <li>
75
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
76
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
76
77
  </li>
77
78
  <li>
78
79
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -633,7 +634,7 @@
633
634
  <footer>
634
635
  <div class="grid">
635
636
  <div class="unit one-third center-on-mobiles">
636
- <p>The contents of this website are <br />&copy;&nbsp;2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
637
+ <p>The contents of this website are <br />&copy;&nbsp;2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
637
638
  </div>
638
639
  <div class="unit two-thirds align-right center-on-mobiles">
639
640
  <p>
@@ -3,7 +3,7 @@
3
3
  <head>
4
4
  <meta charset="UTF-8">
5
5
  <meta name="viewport" content="width=device-width,initial-scale=1">
6
- <meta name="generator" content="Jekyll v3.8.5">
6
+ <meta name="generator" content="Jekyll v3.9.0">
7
7
  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
8
8
  <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
9
9
  <link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
11
11
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
12
12
  <link rel="stylesheet" href="/css/screen.css">
13
13
  <link rel="icon" type="image/x-icon" href="/favicon.ico">
14
- <!-- Begin Jekyll SEO tag v2.5.0 -->
14
+ <!-- Begin Jekyll SEO tag v2.6.1 -->
15
15
  <title>Becoming a Maintainer | Jekyll • Simple, blog-aware, static sites</title>
16
- <meta name="generator" content="Jekyll v3.8.5" />
16
+ <meta name="generator" content="Jekyll v3.9.0" />
17
17
  <meta property="og:title" content="Becoming a Maintainer" />
18
18
  <meta property="og:locale" content="en_US" />
19
19
  <meta name="description" content="This guide is for contributors. These special people have contributed to one or more of Jekyll’s repositories, but do not yet have write access to any. You may find what is written here interesting, but it’s definitely not for everyone." />
@@ -22,12 +22,13 @@
22
22
  <meta property="og:url" content="https://jekyllrb.com/docs/maintaining/becoming-a-maintainer/" />
23
23
  <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
24
24
  <meta property="og:type" content="article" />
25
- <meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
25
+ <meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
26
26
  <meta name="twitter:card" content="summary" />
27
+ <meta property="twitter:title" content="Becoming a Maintainer" />
27
28
  <meta name="twitter:site" content="@jekyllrb" />
28
29
  <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
29
30
  <script type="application/ld+json">
30
- {"headline":"Becoming a Maintainer","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/maintaining/becoming-a-maintainer/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/becoming-a-maintainer/"},"description":"This guide is for contributors. These special people have contributed to one or more of Jekyll’s repositories, but do not yet have write access to any. You may find what is written here interesting, but it’s definitely not for everyone.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
31
+ {"url":"https://jekyllrb.com/docs/maintaining/becoming-a-maintainer/","headline":"Becoming a Maintainer","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"This guide is for contributors. These special people have contributed to one or more of Jekyll’s repositories, but do not yet have write access to any. You may find what is written here interesting, but it’s definitely not for everyone.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/becoming-a-maintainer/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
31
32
  <!-- End Jekyll SEO tag -->
32
33
 
33
34
  <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
72
73
  <div class="meta hide-on-mobiles">
73
74
  <ul>
74
75
  <li>
75
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
76
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
76
77
  </li>
77
78
  <li>
78
79
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -304,7 +305,7 @@
304
305
 
305
306
  <h2 id="2-help-triage-issues">2. Help Triage Issues</h2>
306
307
 
307
- <p>Watch the repository you’re interested in. Join <a href="https://teams.jekyllrb.com">an Affinity Team</a> and receive mentions regarding a particular interest area of the project. When you receive a notification for an issue that has not been triaged by a maintainer, dive in. Can you reproduce the issue? Can you determine the fix? <a href="../triaging-an-issue">More tips on Triaging an Issue in our maintainer guide</a>. Every maintainer loves an issue that is resolved before they get to it. <img class="emoji" title=":smiley:" alt=":smiley:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f603.png" height="20" width="20"></p>
308
+ <p>Watch the repository you’re interested in. Join <a href="https://teams.jekyllrb.com">an Affinity Team</a> and receive mentions regarding a particular interest area of the project. When you receive a notification for an issue that has not been triaged by a maintainer, dive in. Can you reproduce the issue? Can you determine the fix? <a href="../triaging-an-issue">More tips on Triaging an Issue in our maintainer guide</a>. Every maintainer loves an issue that is resolved before they get to it. <img class="emoji" title=":smiley:" alt=":smiley:" src="https://github.githubassets.com/images/icons/emoji/unicode/1f603.png" height="20" width="20"></p>
308
309
 
309
310
  <h2 id="3-write-documentation">3. Write Documentation</h2>
310
311
 
@@ -641,7 +642,7 @@
641
642
  <footer>
642
643
  <div class="grid">
643
644
  <div class="unit one-third center-on-mobiles">
644
- <p>The contents of this website are <br>© 2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
645
+ <p>The contents of this website are <br>© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
645
646
  </div>
646
647
  <div class="unit two-thirds align-right center-on-mobiles">
647
648
  <p>
@@ -3,7 +3,7 @@
3
3
  <head>
4
4
  <meta charset="UTF-8">
5
5
  <meta name="viewport" content="width=device-width,initial-scale=1">
6
- <meta name="generator" content="Jekyll v3.8.5">
6
+ <meta name="generator" content="Jekyll v3.9.0">
7
7
  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
8
8
  <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
9
9
  <link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
11
11
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
12
12
  <link rel="stylesheet" href="/css/screen.css">
13
13
  <link rel="icon" type="image/x-icon" href="/favicon.ico">
14
- <!-- Begin Jekyll SEO tag v2.5.0 -->
14
+ <!-- Begin Jekyll SEO tag v2.6.1 -->
15
15
  <title>Maintaining Jekyll | Jekyll • Simple, blog-aware, static sites</title>
16
- <meta name="generator" content="Jekyll v3.8.5" />
16
+ <meta name="generator" content="Jekyll v3.9.0" />
17
17
  <meta property="og:title" content="Maintaining Jekyll" />
18
18
  <meta property="og:locale" content="en_US" />
19
19
  <meta name="description" content="This guide is for Jekyll contributors and maintainers. These special people contribute to one or more of Jekyll’s repositories or help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone." />
@@ -22,12 +22,13 @@
22
22
  <meta property="og:url" content="https://jekyllrb.com/docs/maintaining/" />
23
23
  <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
24
24
  <meta property="og:type" content="article" />
25
- <meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
25
+ <meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
26
26
  <meta name="twitter:card" content="summary" />
27
+ <meta property="twitter:title" content="Maintaining Jekyll" />
27
28
  <meta name="twitter:site" content="@jekyllrb" />
28
29
  <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
29
30
  <script type="application/ld+json">
30
- {"headline":"Maintaining Jekyll","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/maintaining/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/"},"description":"This guide is for Jekyll contributors and maintainers. These special people contribute to one or more of Jekyll’s repositories or help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
31
+ {"url":"https://jekyllrb.com/docs/maintaining/","headline":"Maintaining Jekyll","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"This guide is for Jekyll contributors and maintainers. These special people contribute to one or more of Jekyll’s repositories or help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
31
32
  <!-- End Jekyll SEO tag -->
32
33
 
33
34
  <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
72
73
  <div class="meta hide-on-mobiles">
73
74
  <ul>
74
75
  <li>
75
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
76
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
76
77
  </li>
77
78
  <li>
78
79
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -638,7 +639,7 @@
638
639
  <footer>
639
640
  <div class="grid">
640
641
  <div class="unit one-third center-on-mobiles">
641
- <p>The contents of this website are <br />&copy;&nbsp;2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
642
+ <p>The contents of this website are <br />&copy;&nbsp;2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
642
643
  </div>
643
644
  <div class="unit two-thirds align-right center-on-mobiles">
644
645
  <p>
@@ -3,7 +3,7 @@
3
3
  <head>
4
4
  <meta charset="UTF-8">
5
5
  <meta name="viewport" content="width=device-width,initial-scale=1">
6
- <meta name="generator" content="Jekyll v3.8.5">
6
+ <meta name="generator" content="Jekyll v3.9.0">
7
7
  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
8
8
  <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
9
9
  <link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
11
11
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
12
12
  <link rel="stylesheet" href="/css/screen.css">
13
13
  <link rel="icon" type="image/x-icon" href="/favicon.ico">
14
- <!-- Begin Jekyll SEO tag v2.5.0 -->
14
+ <!-- Begin Jekyll SEO tag v2.6.1 -->
15
15
  <title>Merging a Pull Request | Jekyll • Simple, blog-aware, static sites</title>
16
- <meta name="generator" content="Jekyll v3.8.5" />
16
+ <meta name="generator" content="Jekyll v3.9.0" />
17
17
  <meta property="og:title" content="Merging a Pull Request" />
18
18
  <meta property="og:locale" content="en_US" />
19
19
  <meta name="description" content="This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone." />
@@ -22,12 +22,13 @@
22
22
  <meta property="og:url" content="https://jekyllrb.com/docs/maintaining/merging-a-pull-request/" />
23
23
  <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
24
24
  <meta property="og:type" content="article" />
25
- <meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
25
+ <meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
26
26
  <meta name="twitter:card" content="summary" />
27
+ <meta property="twitter:title" content="Merging a Pull Request" />
27
28
  <meta name="twitter:site" content="@jekyllrb" />
28
29
  <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
29
30
  <script type="application/ld+json">
30
- {"headline":"Merging a Pull Request","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/maintaining/merging-a-pull-request/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/merging-a-pull-request/"},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
31
+ {"url":"https://jekyllrb.com/docs/maintaining/merging-a-pull-request/","headline":"Merging a Pull Request","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/merging-a-pull-request/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
31
32
  <!-- End Jekyll SEO tag -->
32
33
 
33
34
  <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
72
73
  <div class="meta hide-on-mobiles">
73
74
  <ul>
74
75
  <li>
75
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
76
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
76
77
  </li>
77
78
  <li>
78
79
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -308,7 +309,7 @@
308
309
 
309
310
  <ol>
310
311
  <li>You can’t modify anything on mobile (e.g. titles, labels)</li>
311
- <li>We like to provide a consistent paper trail in the <code class="highlighter-rouge">History.markdown</code> file for each release</li>
312
+ <li>We like to provide a consistent paper trail in the <code class="language-plaintext highlighter-rouge">History.markdown</code> file for each release</li>
312
313
  </ol>
313
314
 
314
315
  <p>To merge a pull request, leave a comment thanking the contributor, then add the special merge request:</p>
@@ -322,25 +323,25 @@
322
323
 
323
324
  <ol>
324
325
  <li>
325
- <code class="highlighter-rouge">@jekyllbot:</code> – this is the prefix our bot looks for when processing commands</li>
326
+ <code class="language-plaintext highlighter-rouge">@jekyllbot:</code> – this is the prefix our bot looks for when processing commands</li>
326
327
  <li>
327
- <code class="highlighter-rouge">merge</code> – the command</li>
328
+ <code class="language-plaintext highlighter-rouge">merge</code> – the command</li>
328
329
  <li>
329
- <code class="highlighter-rouge">+dev</code> – the category to which the changes belong.</li>
330
+ <code class="language-plaintext highlighter-rouge">+dev</code> – the category to which the changes belong.</li>
330
331
  </ol>
331
332
 
332
- <p>The categories match the headings in the <code class="highlighter-rouge">History.markdown</code> file, and they are:</p>
333
+ <p>The categories match the headings in the <code class="language-plaintext highlighter-rouge">History.markdown</code> file, and they are:</p>
333
334
 
334
335
  <ol>
335
- <li>Major Enhancements (<code class="highlighter-rouge">+major</code>) – major updates or breaking changes to the code which necessitate a major version bump (v3 ~&gt; v4)</li>
336
- <li>Minor Enhancements (<code class="highlighter-rouge">+minor</code>) – minor updates (with the labels <code class="highlighter-rouge">feature</code> or <code class="highlighter-rouge">enhancement</code>) which necessitate a minor version bump (v3.1 ~&gt; v3.2)</li>
337
- <li>Bug Fixes (<code class="highlighter-rouge">+bug</code>) – corrections to code which do not change or add functionality, which necessitate a patch version bump (v3.1.0 ~&gt; v3.1.1)</li>
338
- <li>Documentation (<code class="highlighter-rouge">+doc</code>) - changes to the documentation found in <code class="highlighter-rouge">docs/_docs/</code>
336
+ <li>Major Enhancements (<code class="language-plaintext highlighter-rouge">+major</code>) – major updates or breaking changes to the code which necessitate a major version bump (v3 ~&gt; v4)</li>
337
+ <li>Minor Enhancements (<code class="language-plaintext highlighter-rouge">+minor</code>) – minor updates (with the labels <code class="language-plaintext highlighter-rouge">feature</code> or <code class="language-plaintext highlighter-rouge">enhancement</code>) which necessitate a minor version bump (v3.1 ~&gt; v3.2)</li>
338
+ <li>Bug Fixes (<code class="language-plaintext highlighter-rouge">+bug</code>) – corrections to code which do not change or add functionality, which necessitate a patch version bump (v3.1.0 ~&gt; v3.1.1)</li>
339
+ <li>Documentation (<code class="language-plaintext highlighter-rouge">+doc</code>) - changes to the documentation found in <code class="language-plaintext highlighter-rouge">docs/_docs/</code>
339
340
  </li>
340
- <li>Site Enhancements (<code class="highlighter-rouge">+site</code>) – changes to the source of <a href="https://jekyllrb.com">https://jekyllrb.com</a> found in <code class="highlighter-rouge">docs/</code>
341
+ <li>Site Enhancements (<code class="language-plaintext highlighter-rouge">+site</code>) – changes to the source of <a href="https://jekyllrb.com">https://jekyllrb.com</a> found in <code class="language-plaintext highlighter-rouge">docs/</code>
341
342
  </li>
342
- <li>Development Fixes (<code class="highlighter-rouge">+dev</code>) – changes which do not affect user-facing functionality or documentation, such as test fixes or bumping internal dependencies</li>
343
- <li>Forward Ports (<code class="highlighter-rouge">+port</code>) — bug fixes applied to a previous version of Jekyll pulled onto <code class="highlighter-rouge">master</code>, e.g. cherry-picked commits from <code class="highlighter-rouge">3-1-stable</code> to <code class="highlighter-rouge">master</code>
343
+ <li>Development Fixes (<code class="language-plaintext highlighter-rouge">+dev</code>) – changes which do not affect user-facing functionality or documentation, such as test fixes or bumping internal dependencies</li>
344
+ <li>Forward Ports (<code class="language-plaintext highlighter-rouge">+port</code>) — bug fixes applied to a previous version of Jekyll pulled onto <code class="language-plaintext highlighter-rouge">master</code>, e.g. cherry-picked commits from <code class="language-plaintext highlighter-rouge">3-1-stable</code> to <code class="language-plaintext highlighter-rouge">master</code>
344
345
  </li>
345
346
  </ol>
346
347
 
@@ -349,14 +350,14 @@
349
350
  <ol>
350
351
  <li>A successful merge</li>
351
352
  <li>Addition of labels for the necessary category if they aren’t already applied</li>
352
- <li>A commit to the <code class="highlighter-rouge">History.markdown</code> file which adds a note about the change</li>
353
+ <li>A commit to the <code class="language-plaintext highlighter-rouge">History.markdown</code> file which adds a note about the change</li>
353
354
  </ol>
354
355
 
355
- <p>If you forget the category, that’s just fine. You can always go back and move the line to the proper category header later. The category is always necessary for <code class="highlighter-rouge">jekyll/jekyll</code>, but many plugins have too few changes to necessitate changelog categories.</p>
356
+ <p>If you forget the category, that’s just fine. You can always go back and move the line to the proper category header later. The category is always necessary for <code class="language-plaintext highlighter-rouge">jekyll/jekyll</code>, but many plugins have too few changes to necessitate changelog categories.</p>
356
357
 
357
358
  <h2 id="rejoice">Rejoice</h2>
358
359
 
359
- <p>You did it! Thanks for being a maintainer for one of our official Jekyll projects. Your work means the world to our thousands of users who rely on Jekyll daily. <img class="emoji" title=":heart:" alt=":heart:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/2764.png" height="20" width="20"></p>
360
+ <p>You did it! Thanks for being a maintainer for one of our official Jekyll projects. Your work means the world to our thousands of users who rely on Jekyll daily. <img class="emoji" title=":heart:" alt=":heart:" src="https://github.githubassets.com/images/icons/emoji/unicode/2764.png" height="20" width="20"></p>
360
361
 
361
362
 
362
363
 
@@ -671,7 +672,7 @@
671
672
  <footer>
672
673
  <div class="grid">
673
674
  <div class="unit one-third center-on-mobiles">
674
- <p>The contents of this website are <br>© 2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
675
+ <p>The contents of this website are <br>© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
675
676
  </div>
676
677
  <div class="unit two-thirds align-right center-on-mobiles">
677
678
  <p>
@@ -3,7 +3,7 @@
3
3
  <head>
4
4
  <meta charset="UTF-8">
5
5
  <meta name="viewport" content="width=device-width,initial-scale=1">
6
- <meta name="generator" content="Jekyll v3.8.5">
6
+ <meta name="generator" content="Jekyll v3.9.0">
7
7
  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
8
8
  <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
9
9
  <link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
11
11
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
12
12
  <link rel="stylesheet" href="/css/screen.css">
13
13
  <link rel="icon" type="image/x-icon" href="/favicon.ico">
14
- <!-- Begin Jekyll SEO tag v2.5.0 -->
14
+ <!-- Begin Jekyll SEO tag v2.6.1 -->
15
15
  <title>Releasing a new version | Jekyll • Simple, blog-aware, static sites</title>
16
- <meta name="generator" content="Jekyll v3.8.5" />
16
+ <meta name="generator" content="Jekyll v3.9.0" />
17
17
  <meta property="og:title" content="Releasing a new version" />
18
18
  <meta property="og:locale" content="en_US" />
19
19
  <meta name="description" content="This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone." />
@@ -22,12 +22,13 @@
22
22
  <meta property="og:url" content="https://jekyllrb.com/docs/maintaining/releasing-a-new-version/" />
23
23
  <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
24
24
  <meta property="og:type" content="article" />
25
- <meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
25
+ <meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
26
26
  <meta name="twitter:card" content="summary" />
27
+ <meta property="twitter:title" content="Releasing a new version" />
27
28
  <meta name="twitter:site" content="@jekyllrb" />
28
29
  <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
29
30
  <script type="application/ld+json">
30
- {"headline":"Releasing a new version","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/maintaining/releasing-a-new-version/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/releasing-a-new-version/"},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
31
+ {"url":"https://jekyllrb.com/docs/maintaining/releasing-a-new-version/","headline":"Releasing a new version","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/releasing-a-new-version/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
31
32
  <!-- End Jekyll SEO tag -->
32
33
 
33
34
  <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
72
73
  <div class="meta hide-on-mobiles">
73
74
  <ul>
74
75
  <li>
75
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
76
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
76
77
  </li>
77
78
  <li>
78
79
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -300,7 +301,7 @@
300
301
 
301
302
  <h3 id="bump-the-version">Bump the version</h3>
302
303
 
303
- <p>The only important place you need to manually bump the version is in <code class="highlighter-rouge">lib/jekyll/version.rb</code>. Adjust that, and everything else should work fine.</p>
304
+ <p>The only important place you need to manually bump the version is in <code class="language-plaintext highlighter-rouge">lib/jekyll/version.rb</code>. Adjust that, and everything else should work fine.</p>
304
305
 
305
306
  <h3 id="update-the-history-document">Update the history document</h3>
306
307
 
@@ -310,7 +311,7 @@
310
311
  </span><span class="gi">+## 3.7.1 / 2018-01-25
311
312
  </span></code></pre></div></div>
312
313
 
313
- <p>Adjust the version number and the date. The <code class="highlighter-rouge">## HEAD</code> heading will be regenerated next time a pull request is merged.</p>
314
+ <p>Adjust the version number and the date. The <code class="language-plaintext highlighter-rouge">## HEAD</code> heading will be regenerated next time a pull request is merged.</p>
314
315
 
315
316
  <p>Once you’ve done this, update the website by running the following command:</p>
316
317
 
@@ -319,21 +320,21 @@
319
320
 
320
321
  <p>This updates the website’s changelog, and pushes the versions in various other places.</p>
321
322
 
322
- <p>It’s recommended that you go over the <code class="highlighter-rouge">History.markdown</code> file manually one more time, in case there are any spelling errors or such. Feel free to fix those manually, and after you’re done generating the website changelog, commit your changes.</p>
323
+ <p>It’s recommended that you go over the <code class="language-plaintext highlighter-rouge">History.markdown</code> file manually one more time, in case there are any spelling errors or such. Feel free to fix those manually, and after you’re done generating the website changelog, commit your changes.</p>
323
324
 
324
325
  <h2 id="write-a-release-post">Write a release post</h2>
325
326
 
326
- <p>In case this isn’t done already, you can generate a new release post using the included <code class="highlighter-rouge">rake</code> command:</p>
327
+ <p>In case this isn’t done already, you can generate a new release post using the included <code class="language-plaintext highlighter-rouge">rake</code> command:</p>
327
328
 
328
329
  <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>bundle <span class="nb">exec </span>rake site:releases:new[3.8.0]
329
330
  </code></pre></div></div>
330
331
 
331
- <p>where <code class="highlighter-rouge">3.8.0</code> should be replaced with the new version. Then, write the post. Be sure to thank all of the collaborators and maintainers who have contributed since the last release. You can generate a log of their names using the following command:</p>
332
+ <p>where <code class="language-plaintext highlighter-rouge">3.8.0</code> should be replaced with the new version. Then, write the post. Be sure to thank all of the collaborators and maintainers who have contributed since the last release. You can generate a log of their names using the following command:</p>
332
333
 
333
334
  <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git shortlog <span class="nt">-sn</span> master...v3.7.2
334
335
  </code></pre></div></div>
335
336
 
336
- <p>where, again <code class="highlighter-rouge">v3.7.2</code> is the last release. Be sure to open a pull request for your release post.</p>
337
+ <p>where, again <code class="language-plaintext highlighter-rouge">v3.7.2</code> is the last release. Be sure to open a pull request for your release post.</p>
337
338
 
338
339
  <h3 id="push-the-version">Push the version</h3>
339
340
 
@@ -343,7 +344,7 @@
343
344
  <li>You have permission to push a new gem version to RubyGems</li>
344
345
  <li>You’re logged into RubyGems on your command line</li>
345
346
  <li>A release post has been prepared, and is ideally already live</li>
346
- <li>All of the prior steps are done, committed, and pushed to <code class="highlighter-rouge">master</code>
347
+ <li>All of the prior steps are done, committed, and pushed to <code class="language-plaintext highlighter-rouge">master</code>
347
348
  </li>
348
349
  </ul>
349
350
 
@@ -354,19 +355,19 @@
354
355
 
355
356
  <p>This will automatically build the new gem, make a release commit and tag and then push the new gem to RubyGems. Don’t worry about creating a GitHub release, <a href="https://github.com/jekyllbot" class="user-mention">@jekyllbot</a> should take care of that.</p>
356
357
 
357
- <p>And then, you’re done! <img class="emoji" title=":tada:" alt=":tada:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f389.png" height="20" width="20"> Feel free to celebrate!</p>
358
+ <p>And then, you’re done! <img class="emoji" title=":tada:" alt=":tada:" src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png" height="20" width="20"> Feel free to celebrate!</p>
358
359
 
359
360
  <p>If you have access to the <a href="https://twitter.com/jekyllrb">@jekyllrb</a> Twitter account, you should tweet the release post from there. If not, just ask another maintainer to do it or to give you access.</p>
360
361
 
361
362
  <h2 id="for-non-core-gems">For non-core gems</h2>
362
363
 
363
- <p>If you’re not a maintainer for <code class="highlighter-rouge">jekyll/jekyll</code>, the procedure is much simpler in a lot of cases. Generally, the procedure still looks like this:</p>
364
+ <p>If you’re not a maintainer for <code class="language-plaintext highlighter-rouge">jekyll/jekyll</code>, the procedure is much simpler in a lot of cases. Generally, the procedure still looks like this:</p>
364
365
 
365
366
  <ul>
366
- <li>Bump the gem version manually, usually in <code class="highlighter-rouge">lib/&lt;plugin_name&gt;/version.rb</code>
367
+ <li>Bump the gem version manually, usually in <code class="language-plaintext highlighter-rouge">lib/&lt;plugin_name&gt;/version.rb</code>
367
368
  </li>
368
369
  <li>Adjust the history file</li>
369
- <li>Run <code class="highlighter-rouge">bundle exec rake release</code> or <code class="highlighter-rouge">script/release</code>, depending on which of the two exists</li>
370
+ <li>Run <code class="language-plaintext highlighter-rouge">bundle exec rake release</code> or <code class="language-plaintext highlighter-rouge">script/release</code>, depending on which of the two exists</li>
370
371
  <li>Rejoice</li>
371
372
  </ul>
372
373
 
@@ -685,7 +686,7 @@
685
686
  <footer>
686
687
  <div class="grid">
687
688
  <div class="unit one-third center-on-mobiles">
688
- <p>The contents of this website are <br>© 2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
689
+ <p>The contents of this website are <br>© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
689
690
  </div>
690
691
  <div class="unit two-thirds align-right center-on-mobiles">
691
692
  <p>
@@ -3,7 +3,7 @@
3
3
  <head>
4
4
  <meta charset="UTF-8">
5
5
  <meta name="viewport" content="width=device-width,initial-scale=1">
6
- <meta name="generator" content="Jekyll v3.8.5">
6
+ <meta name="generator" content="Jekyll v3.9.0">
7
7
  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
8
8
  <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
9
9
  <link rel="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
11
11
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
12
12
  <link rel="stylesheet" href="/css/screen.css">
13
13
  <link rel="icon" type="image/x-icon" href="/favicon.ico">
14
- <!-- Begin Jekyll SEO tag v2.5.0 -->
14
+ <!-- Begin Jekyll SEO tag v2.6.1 -->
15
15
  <title>Reviewing a Pull Request | Jekyll • Simple, blog-aware, static sites</title>
16
- <meta name="generator" content="Jekyll v3.8.5" />
16
+ <meta name="generator" content="Jekyll v3.9.0" />
17
17
  <meta property="og:title" content="Reviewing a Pull Request" />
18
18
  <meta property="og:locale" content="en_US" />
19
19
  <meta name="description" content="This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone." />
@@ -22,12 +22,13 @@
22
22
  <meta property="og:url" content="https://jekyllrb.com/docs/maintaining/reviewing-a-pull-request/" />
23
23
  <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
24
24
  <meta property="og:type" content="article" />
25
- <meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
25
+ <meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
26
26
  <meta name="twitter:card" content="summary" />
27
+ <meta property="twitter:title" content="Reviewing a Pull Request" />
27
28
  <meta name="twitter:site" content="@jekyllrb" />
28
29
  <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
29
30
  <script type="application/ld+json">
30
- {"headline":"Reviewing a Pull Request","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/maintaining/reviewing-a-pull-request/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/reviewing-a-pull-request/"},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
31
+ {"url":"https://jekyllrb.com/docs/maintaining/reviewing-a-pull-request/","headline":"Reviewing a Pull Request","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/maintaining/reviewing-a-pull-request/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
31
32
  <!-- End Jekyll SEO tag -->
32
33
 
33
34
  <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
72
73
  <div class="meta hide-on-mobiles">
73
74
  <ul>
74
75
  <li>
75
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
76
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
76
77
  </li>
77
78
  <li>
78
79
  <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -300,7 +301,7 @@
300
301
 
301
302
  <p>Above all else, please review a pull request kindly. Our community can only be strong if we make it a welcoming and inclusive environment. To further promote this, the Jekyll community is governed by a <a href="/docs/conduct/">Code of Conduct</a> by which all community members must abide.</p>
302
303
 
303
- <p>Use emoji liberally <img class="emoji" title=":heart:" alt=":heart:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/2764.png" height="20" width="20"> <img class="emoji" title=":tada:" alt=":tada:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f389.png" height="20" width="20"> <img class="emoji" title=":sparkles:" alt=":sparkles:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/2728.png" height="20" width="20"> <img class="emoji" title=":confetti_ball:" alt=":confetti_ball:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f38a.png" height="20" width="20"> and feel free to be emotive!! Contributions keep this project moving forward and we’re always happy to receive them, even if the pull request isn’t ultimately merged.</p>
304
+ <p>Use emoji liberally <img class="emoji" title=":heart:" alt=":heart:" src="https://github.githubassets.com/images/icons/emoji/unicode/2764.png" height="20" width="20"> <img class="emoji" title=":tada:" alt=":tada:" src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png" height="20" width="20"> <img class="emoji" title=":sparkles:" alt=":sparkles:" src="https://github.githubassets.com/images/icons/emoji/unicode/2728.png" height="20" width="20"> <img class="emoji" title=":confetti_ball:" alt=":confetti_ball:" src="https://github.githubassets.com/images/icons/emoji/unicode/1f38a.png" height="20" width="20"> and feel free to be emotive!! Contributions keep this project moving forward and we’re always happy to receive them, even if the pull request isn’t ultimately merged.</p>
304
305
 
305
306
  <p>Mike McQuaid’s post on the GitHub blog entitled <a href="https://github.com/blog/2124-kindly-closing-pull-requests">“Kindly Closing Pull Requests”</a> is a great place to start. It describes various scenarios in which it would be acceptable to close a pull request for reasons other than lack of technical integrity or accuracy. Part of being kind is responding to and resolving pull requests quickly.</p>
306
307
 
@@ -308,7 +309,7 @@
308
309
 
309
310
  <p>We should be able to review all pull requests within one week. The only time initial review should take longer is if all the maintainers mysteriously took vacation during the same week. Promptness encourages frequent, high-quality contributions from community members and other maintainers.</p>
310
311
 
311
- <p>If your response requires a response on the part of the author, please add the <code class="highlighter-rouge">pending-feedback</code> tag. <a href="https://github.com/jekyllbot" class="user-mention">@jekyllbot</a> will automatically remove the tag once the author of the pull request responds.</p>
312
+ <p>If your response requires a response on the part of the author, please add the <code class="language-plaintext highlighter-rouge">pending-feedback</code> tag. <a href="https://github.com/jekyllbot" class="user-mention">@jekyllbot</a> will automatically remove the tag once the author of the pull request responds.</p>
312
313
 
313
314
  <h2 id="resolve-quickly">Resolve Quickly</h2>
314
315
 
@@ -649,7 +650,7 @@
649
650
  <footer>
650
651
  <div class="grid">
651
652
  <div class="unit one-third center-on-mobiles">
652
- <p>The contents of this website are <br>© 2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
653
+ <p>The contents of this website are <br>© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
653
654
  </div>
654
655
  <div class="unit two-thirds align-right center-on-mobiles">
655
656
  <p>