repo sync

Author: Octomerger

content/actions/reference/context-and-expression-syntax-for-github-actions.md

@@ -186,27 +186,27 @@ jobs:
     steps:
       - name: Dump GitHub context
         env:
-          GITHUB_CONTEXT: ${{ toJson(github) }}
+          GITHUB_CONTEXT: ${{ toJSON(github) }}
         run: echo "$GITHUB_CONTEXT"
       - name: Dump job context
         env:
-          JOB_CONTEXT: ${{ toJson(job) }}
+          JOB_CONTEXT: ${{ toJSON(job) }}
         run: echo "$JOB_CONTEXT"
       - name: Dump steps context
         env:
-          STEPS_CONTEXT: ${{ toJson(steps) }}
+          STEPS_CONTEXT: ${{ toJSON(steps) }}
         run: echo "$STEPS_CONTEXT"
       - name: Dump runner context
         env:
-          RUNNER_CONTEXT: ${{ toJson(runner) }}
+          RUNNER_CONTEXT: ${{ toJSON(runner) }}
         run: echo "$RUNNER_CONTEXT"
       - name: Dump strategy context
         env:
-          STRATEGY_CONTEXT: ${{ toJson(strategy) }}
+          STRATEGY_CONTEXT: ${{ toJSON(strategy) }}
         run: echo "$STRATEGY_CONTEXT"
       - name: Dump matrix context
         env:
-          MATRIX_CONTEXT: ${{ toJson(matrix) }}
+          MATRIX_CONTEXT: ${{ toJSON(matrix) }}
         run: echo "$MATRIX_CONTEXT"
 ```
 {% endraw %}
@@ -348,7 +348,7 @@ The value for `array` can be an array or a string. All values in `array` are con
 
 `join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted'
 
-#### toJson
+#### toJSON
 
 `toJSON(value)`
 
@@ -358,13 +358,13 @@ Returns a pretty-print JSON representation of `value`. You can use this function
 
 `toJSON(job)` might return `{ "status": "Success" }`
 
-#### fromJson
+#### fromJSON
 
 `fromJSON(value)`
 
-Returns a JSON object for `value`. You can use this function to provide a JSON object as an evaluated expression.
+Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string.
 
-##### Example
+##### Example returning a JSON object
 
 This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`.
 
@@ -384,12 +384,33 @@ jobs:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
-      matrix: ${{fromJson(needs.job1.outputs.matrix)}}
+      matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
     - run: build
 ```
 {% endraw %}
 
+##### Example returning a JSON data type
+
+This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer.
+
+{% raw %}
+```yaml
+name: print
+on: push
+env: 
+  continue: true
+  time: 3
+jobs:
+  job1:
+    runs-on: ubuntu-latest
+    steps:
+    - continue-on-error: ${{ fromJSON(env.continue) }}
+      timeout-minutes: ${{ fromJSON(env.time) }}
+      run: echo ...
+```
+{% endraw %}
+
 #### hashFiles
 
 `hashFiles(path)`

lib/redirects/precompile.js

@@ -1,9 +1,6 @@
-const patterns = require('../patterns')
 const { latest } = require('../enterprise-server-releases')
-const getOldPathsFromPermalink = require('../redirects/get-old-paths-from-permalink')
 const getDocsPathFromDevPath = require('../redirects/get-docs-path-from-developer-path')
 const DEVELOPER_ROUTES = require('../redirects/static/developer-docs-routes-for-supported-versions')
-const ARCHIVED_ROUTES = require('../redirects/static/archived-routes-from-213-to-217')
 
 // This function runs at server warmup and precompiles possible redirect routes.
 // It outputs them in key-value pairs within a neat Javascript object: { oldPath: newPath }
@@ -14,26 +11,7 @@ module.exports = function precompileRedirects (pageList, pageMap) {
   // create backwards-compatible old paths for page permalinks and frontmatter redirects
   pageList.forEach(page => Object.assign(allRedirects, page.buildRedirects()))
 
-  // 2. REDIRECTS FOR ARCHIVED ROUTES FROM 2.13 TO 2.17
-  // Starting with 2.18, we updated the archival script to create stubbed HTML redirect files,
-  // so those files do the heavy lifting. The handling here is only for blanket redirects
-  // (like /articles -> /github) between 2.13 and 2.17. This works by creating possible
-  // old/incoming paths from the archived routes JSON. Frontmatter redirects were lost
-  // for 2.13-2.17, but the archived middleware tries to find fallbacks.
-  ARCHIVED_ROUTES.forEach(archivedRoute => {
-    const languageFromPath = archivedRoute.match(patterns.getLanguageCode)[1]
-    const versionFromPath = archivedRoute.match(patterns.getEnterpriseVersionNumber)[1]
-
-    // get an array of possible old paths, e.g., /desktop/guides/ from /desktop/
-    const possibleOldPaths = getOldPathsFromPermalink(archivedRoute, languageFromPath, versionFromPath)
-
-    // for each old path, add a redirect to the current route
-    possibleOldPaths.forEach(oldPath => {
-      allRedirects[oldPath] = archivedRoute
-    })
-  })
-
-  // 3. DEVELOPER ROUTES FOR CURRENTLY SUPPORTED VERSIONS
+  // 2. DEVELOPER ROUTES FOR CURRENTLY SUPPORTED VERSIONS
   // From the list of developer docs routes, create new docs.github.com-style paths.
   // Note that the list only includes supported enterprise paths up to 2.21, which is
   // the last version that was available on developer.github.com before the migration.