Merge branch 'master' into master

Author: kenyonj

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,5 @@
 - [ ] Have you followed the [contributing guidelines](https://github.com/github/opensource.guide/blob/master/CONTRIBUTING.md)?
 - [ ] Have you explained what your changes do, and why they add value to the Guides?
-- [ ] Have you enabled GitHub Pages Previews by pressing <keyboard>`Enable GitHub Pages`</keyboard> on the right sidebar to trigger a pages build for this PR?
 
 **Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.**
 

.github/main.workflow

@@ -0,0 +1,19 @@
+workflow "test" {
+  resolves = ["CI Test Runner"]
+  on = "push"
+}
+
+action "CI Test Runner" {
+  uses = "./.github/test_runner"
+  secrets = ["GITHUB_TOKEN"]
+}
+
+workflow "build" {
+  on = "push"
+  resolves = ["Jekyll Pages Builder"]
+}
+
+action "Jekyll Pages Builder" {
+  uses = "./.github/pages_builder"
+  secrets = ["GITHUB_TOKEN"]
+}

.github/pages_builder/Dockerfile

@@ -0,0 +1,14 @@
+FROM jekyll/jekyll
+
+LABEL "com.github.actions.name"="Jekyll Pages Builder"
+LABEL "com.github.actions.description"="Build the full jekyll pages site"
+LABEL "com.github.actions.icon"="gear"
+LABEL "com.github.actions.color"="purple"
+
+ENV LC_ALL C.UTF-8
+ENV LANG en_US.UTF-8
+ENV LANGUAGE en_US.UTF-8
+
+COPY entrypoint.sh /
+
+ENTRYPOINT ["/entrypoint.sh"]

.github/pages_builder/entrypoint.sh

@@ -0,0 +1,5 @@
+#!/bin/sh -l
+
+script/bootstrap
+cd test && npm install && cd ..
+JEKYLL_GITHUB_TOKEN=$GITHUB_TOKEN script/build

.github/test_runner/Dockerfile

@@ -0,0 +1,14 @@
+FROM jekyll/jekyll
+
+LABEL "com.github.actions.name"="CI Test Runner"
+LABEL "com.github.actions.description"="Run the full test suite"
+LABEL "com.github.actions.icon"="gear"
+LABEL "com.github.actions.color"="purple"
+
+ENV LC_ALL C.UTF-8
+ENV LANG en_US.UTF-8
+ENV LANGUAGE en_US.UTF-8
+
+COPY entrypoint.sh /
+
+ENTRYPOINT ["/entrypoint.sh"]

.github/test_runner/entrypoint.sh

@@ -0,0 +1,5 @@
+#!/bin/sh -l
+
+script/bootstrap
+cd test && npm install && cd ..
+JEKYLL_GITHUB_TOKEN=$GITHUB_TOKEN script/test

.travis.yml

@@ -1,7 +1,7 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.10)
+    activesupport (4.2.11.1)
       i18n (~> 0.7)
       minitest (~> 5.1)
       thread_safe (~> 0.3, >= 0.3.4)
@@ -31,10 +31,10 @@ GEM
     ffi (1.10.0)
     forwardable-extended (2.6.0)
     gemoji (3.0.0)
-    github-pages (197)
-      activesupport (= 4.2.10)
+    github-pages (198)
+      activesupport (= 4.2.11.1)
       github-pages-health-check (= 1.16.1)
-      jekyll (= 3.7.4)
+      jekyll (= 3.8.5)
       jekyll-avatar (= 0.6.0)
       jekyll-coffeescript (= 1.1.1)
       jekyll-commonmark-ghpages (= 0.1.5)
@@ -82,7 +82,7 @@ GEM
       octokit (~> 4.0)
       public_suffix (~> 3.0)
       typhoeus (~> 1.3)
-    html-pipeline (2.10.0)
+    html-pipeline (2.11.0)
       activesupport (>= 2)
       nokogiri (>= 1.4)
     html-proofer (3.10.2)
@@ -97,7 +97,7 @@ GEM
     http_parser.rb (0.6.0)
     i18n (0.9.5)
       concurrent-ruby (~> 1.0)
-    jekyll (3.7.4)
+    jekyll (3.8.5)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
@@ -215,7 +215,7 @@ GEM
       jekyll-seo-tag (~> 2.1)
     minitest (5.11.3)
     multipart-post (2.0.0)
-    nokogiri (1.10.2)
+    nokogiri (1.10.3)
       mini_portile2 (~> 2.4.0)
     octokit (4.14.0)
       sawyer (~> 0.8.0, >= 0.5.3)

Gemfile.lock

@@ -175,7 +175,7 @@ Sie können Ihre README verwenden, um andere Fragen zu beantworten: z.B. wie Sie
 
 Manchmal vermeiden es Leute, eine README zu schreiben, weil sie das Gefühl haben, das Projekt sei unvollendet, oder weil sie keine Beiträge wollen. Aber auch dies sind gute Gründe, eine zu schreiben.
 
-Weitere Inspirationen zum Schreiben einer README finden Sie in @18F's ["Making READMEs Readable"](https://pages.18f.gov/open-source-guide/making-readmes-readable/) oder in @PurpleBooth's [README template](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2).
+Weitere Inspirationen zum Schreiben einer README finden Sie in @dguo's ["Make a README"-Anleitung](https://www.makeareadme.com/) oder in @PurpleBooth's [README-Vorlage](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2).
 
 Wenn Sie eine README-Datei im Hauptordner Ihres Projektes anlegen, zeigt GitHub diese automatisch auf der Homepage des Repos an.
 

_articles/de/starting-a-project.md

@@ -165,7 +165,7 @@ You can use your README to answer other questions, like how you handle contribut
 
 Sometimes, people avoid writing a README because they feel like the project is unfinished, or they don't want contributions. These are all very good reasons to write one.
 
-For more inspiration, try using @18F's ["Making READMEs Readable"](https://pages.18f.gov/open-source-guide/making-readmes-readable/) or @PurpleBooth's [README template](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2) to write a complete README.
+For more inspiration, try using @dguo's ["Make a README" guide](https://www.makeareadme.com/) or @PurpleBooth's [README template](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2) to write a complete README.
 
 When you include a README file in the root directory, GitHub will automatically display it on the repository homepage.