From aed803ac39a26d2c92b1d5a8b9242dd4b13726cd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=B3bert=20Papp?= Date: Mon, 8 Apr 2024 23:04:45 +0100 Subject: [PATCH] Complete list of GITHUB_ vars that are exceptionally not _PATH suffixed. (#32407) Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> --- content/actions/learn-github-actions/variables.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/actions/learn-github-actions/variables.md b/content/actions/learn-github-actions/variables.md index 5f8ff46ea3..3bb7f753d6 100644 --- a/content/actions/learn-github-actions/variables.md +++ b/content/actions/learn-github-actions/variables.md @@ -75,8 +75,6 @@ Because runner environment variable interpolation is done after a workflow job i When you set an environment variable, you cannot use any of the default environment variable names. For a complete list of default environment variables, see "[Default environment variables](#default-environment-variables)" below. If you attempt to override the value of one of these default variables, the assignment is ignored. -Any new variables you set that point to a location on the filesystem should have a `_PATH` suffix. The `GITHUB_ENV` and `GITHUB_WORKSPACE` default variables are exceptions to this convention. - {% note %} **Note**: You can list the entire set of environment variables that are available to a workflow step by using `run: env` in a step and then examining the output for the step.