From 5c1c5b58211bfe090d9aa04eb53f3b8e76cb1771 Mon Sep 17 00:00:00 2001 From: Jason Etcovitch Date: Tue, 20 Aug 2019 22:15:05 -0700 Subject: [PATCH 1/2] Highlight codeblocks in core/README.md --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f9cc0c3..d60fc5c 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ You can use this library to get inputs or set outputs: -``` +```js const core = require('@actions/core'); const myInput = core.getInput('inputName', { required: true }); @@ -22,7 +22,7 @@ core.setOutput('outputKey', 'outputVal'); You can also export variables and secrets for future steps. Variables get set in the environment automatically, while secrets must be scoped into the environment from a workflow using `${{ secrets.FOO }}`. Secrets will also be masked from the logs: -``` +```js const core = require('@actions/core'); // Do stuff @@ -45,7 +45,7 @@ core.addPath('pathToTool'); You should use this library to set the failing exit code for your action: -``` +```js const core = require('@actions/core'); try { @@ -62,7 +62,7 @@ catch (err) { Finally, this library provides some utilities for logging. Note that debug logging is hidden from the logs by default. This behavior can be toggled by enabling the [Step Debug Logs](../../docs/action-debugging.md#step-debug-logs). -``` +```js const core = require('@actions/core'); const myInput = core.getInput('input'); From 30ddd36ae4978231664853acc98f0de63d8ba473 Mon Sep 17 00:00:00 2001 From: Jason Etcovitch Date: Wed, 21 Aug 2019 01:16:47 -0400 Subject: [PATCH 2/2] Missed one --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d60fc5c..ade0b6f 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ core.exportSecret('secretVar', variableWithSecretValue); You can explicitly add items to the path for all remaining steps in a workflow: -``` +```js const core = require('@actions/core'); core.addPath('pathToTool');