The GITHUB_STATE file is only available within an action. For more information on the post: action, see ' Metadata syntax for GitHub Actions.' If you have multiple pre: or post: actions, you can only access the saved value in the action where it was written to GITHUB_STATE. Alternatively, you could create a file with the main: action, pass the file location to the post: action, and also use the post: action to delete the file. For example, you can create a file with the pre: action, pass the file location to the main: action, and then use the post: action to delete the file. You can create environment variables for sharing with your workflow's pre: or post: actions by writing to the file located at GITHUB_STATE. Write-Output '::warning:: This is a warning again, because stop-commands has been turned off.' Sending values to the pre and post actions Write-Output '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' Write-Output '::stop-commands::$stopMarker' Write-Output '::warning:: This is a warning message, to demonstrate that commands are being processed.' YAML jobs: workflow-command-job: runs-on: windows-latest steps: - name: Disable workflow commands run: | For more information, see ' Enabling debug logging.' You must create a secret named ACTIONS_STEP_DEBUG with the value true to see the debug messages set by this command in the log. Used as a shortcut for ::error and exit 1Īccessible using environment file GITHUB_OUTPUT The following table shows which toolkit functions are available within a workflow: Toolkit functionĪccessible using environment file GITHUB_PATHĪccessible using environment file GITHUB_ENVĪccessible using environment variable INPUT_Īccessible using environment variable RUNNER_DEBUGĪccessible using environment file GITHUB_STEP_SUMMARYĪccessible using environment file GITHUB_STATE

YAML - name: Create annotation for build error run: Write-Output '::error file=app.js,line=1::Missing semicolon'

Application of core shell