From a3290166dc11ccb5f3c95bd9f10fca876d5f4994 Mon Sep 17 00:00:00 2001 From: Ashwin Maroli Date: Fri, 28 Jan 2022 15:06:02 +0530 Subject: [PATCH] Improve note on use of `actions/cache` [skip ci] --- docs/_docs/continuous-integration/github-actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_docs/continuous-integration/github-actions.md b/docs/_docs/continuous-integration/github-actions.md index e5513bdf..25ce27a1 100644 --- a/docs/_docs/continuous-integration/github-actions.md +++ b/docs/_docs/continuous-integration/github-actions.md @@ -132,7 +132,7 @@ The above workflow can be explained as the following: the Action from overwriting the `gh-pages` branch on any feature branch pushes. - The **name** of the job matches our YAML filename: `github-pages`. - The **checkout** action takes care of cloning your repository. -- The **cache** action is an optimisation for shorten the build times. +- The **cache** action is an optimization to avoid fetching and installing gems on every build. - We specify our selected **action** and **version number** using `helaili/jekyll-action@2.0.5`. This handles the build and deploy. - We set a reference to a secret **environment variable** for the action to use. The `GITHUB_TOKEN`