You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/content/docs/reference/glossary.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -560,7 +560,7 @@ Controls behavior when OTLP endpoint or header values resolve to empty at runtim
560
560
561
561
### Setup-Steps (`jobs.<job-id>.setup-steps`)
562
562
563
-
Steps injected immediately after the compiler-generated `actions/setup` step for a custom or built-in job. Defined under `jobs.<job-id>.setup-steps` in workflow frontmatter. When both a main workflow and an imported workflow define `setup-steps` for the same job, imported setup-steps run first. `setup-steps` remain distinct from `pre-steps` and are not merged across keys. See [Custom Jobs](/gh-aw/reference/steps-jobs/#jobs-and-steps).
563
+
Steps injected immediately after the compiler-generated `actions/setup` step for a custom or built-in job. Defined under `jobs.<job-id>.setup-steps` in workflow frontmatter. When both a main workflow and an imported workflow define `setup-steps` for the same job, imported setup-steps run first. `setup-steps` remain distinct from `pre-steps` and are not merged across keys. `jobs.activation.setup-steps` and `jobs.pre_activation`/`jobs.pre-activation` `setup-steps` are refused at compile time because they can short-circuit protections. See [Custom Jobs](/gh-aw/reference/steps-jobs/#jobs-and-steps).
Copy file name to clipboardExpand all lines: docs/src/content/docs/reference/steps-jobs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ jobs:
80
80
| `continue-on-error` | Allow the workflow to continue if this job fails |
81
81
| `container` | Docker container to run steps in |
82
82
| `services` | Service containers (e.g. databases) |
83
-
| `setup-steps` | Steps injected immediately after the compiler-generated `actions/setup` step for that job |
83
+
| `setup-steps` | Steps injected immediately after the compiler-generated `actions/setup` step for that job (except `activation` and `pre_activation`, where compile fails) |
84
84
| `pre-steps` | Steps injected after compiler setup steps and before checkout/`steps` in that job |
85
85
| `steps` | List of steps — supports complete GitHub Actions step specification |
86
86
| `uses` | Reusable workflow to call |
@@ -120,8 +120,8 @@ Use this map to see where compiler-inserted steps land for each job type.
| `pre_activation` | `jobs.pre_activation.setup-steps` is refused at compile time to prevent short-circuiting protections; use `jobs.pre_activation.pre-steps` and `jobs.pre_activation.steps` |
124
+
| `activation` | `jobs.activation.setup-steps` is refused at compile time to prevent short-circuiting protections; use `jobs.activation.pre-steps` |
"description": "Optional setup steps inserted after setup-injected steps and before any token-mint or checkout steps in this job. Uses the same schema as `steps`."
2458
+
"description": "Optional setup steps inserted after setup-injected steps and before any token-mint or checkout steps in this job. Uses the same schema as `steps`. Not supported for jobs.activation, jobs.pre_activation, or jobs.pre-activation; compilation fails for those protected jobs because setup-steps could short-circuit protections."
0 commit comments