Contexts: You can use most contexts at any point in your workflow, including when default environment variables would be unavailable.For more information, see " Default environment variables." Default environment variables: These variables exist only on the runner that is executing your job.These variables are intended for use at different points in the workflow: GitHub Actions includes a collection of variables called contexts and a similar collection of variables called default environment variables. If you attempt to dereference a non-existent property, it will evaluate to an empty string. In order to use property dereference syntax, the property name must start with a letter or _ and contain only alphanumeric characters, -, or _. Property dereference syntax: github.sha.For more information, see inputs context.Īs part of an expression, you can access context information using one of two syntaxes. For more information, see needs context.Ĭontains the inputs of a reusable or manually triggered workflow. For more information, see matrix context.Ĭontains the outputs of all jobs that are defined as a dependency of the current job. For more information, see strategy context.Ĭontains the matrix properties defined in the workflow that apply to the current job. Information about the matrix execution strategy for the current job. For more information, see secrets context. For more information, see runner context.Ĭontains the names and values of secrets that are available to a workflow run. Information about the runner that is running the current job. Information about the steps that have been run in the current job. For more information, see job context.įor reusable workflows only, contains outputs of jobs from the reusable workflow. Information about the currently running job. For more information, see github context.Ĭontains environment variables set in a workflow, job, or step. For more information, see " Understanding the risk of script injections." Context name Certain contexts should be treated as untrusted input, as an attacker could insert their own malicious content. Writing contexts code#Warning: When creating workflows and actions, you should always consider whether your code might execute untrusted input from possible attackers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |