From 0b69311011cdffad8314e729f21d086912b33a86 Mon Sep 17 00:00:00 2001 From: Ed Burns Date: Wed, 4 Nov 2020 13:50:18 -0500 Subject: [PATCH] Explain to the ignorant reader where this `STATE_` prefix comes from. Explain to the ignorant reader where this `STATE_` prefix comes from. --- docs/commands.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/commands.md b/docs/commands.md index 905321ab..4df725d3 100644 --- a/docs/commands.md +++ b/docs/commands.md @@ -89,7 +89,7 @@ Save a state to an environmental variable that can later be used in the main or echo "::save-state name=FOO::foovalue" ``` -An environmental variable named `STATE_FOO` will be available to use in the post or main action. See [Sending Values to the pre and post actions](https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#sending-values-to-the-pre-and-post-actions) for more information. +Because `save-state` prepends the string `STATE_` to the name, the environment variable `STATE_FOO` will be available to use in the post or main action. See [Sending Values to the pre and post actions](https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#sending-values-to-the-pre-and-post-actions) for more information. ### Log Level