Document + modifier syntax in bundle run --only help#5760
Conversation
afberg
force-pushed
the
jobs-run-now-only-flag
branch
from
4b5431e to
e34491a
Compare
Approval status: pending
|
`bundle run --only` accepts task keys to run a subset of a job's tasks. A task key may be prefixed with `+` (also run upstream tasks) or suffixed with `+` (also run downstream tasks); document that in the flag's help text. Co-authored-by: Isaac
afberg
force-pushed
the
jobs-run-now-only-flag
branch
from
e34491a to
6ba3ad7
Compare
Add a partial_run case asserting `--only +task_1,task_2+` forwards unchanged to the run-now `only` field, proving the CLI does not mangle or reject the upstream/downstream modifier syntax documented on the flag. Co-authored-by: Isaac
|
An authorized user can trigger integration tests manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
1 participant
Changes
bundle run --onlytakes a comma-separated list of task keys to run a subset of a job's tasks. Its help text did not mention that a task key can be prefixed or suffixed with+to also pull in upstream/downstream tasks (the value is forwarded to therun-nowonlyAPI field, which interprets the modifiers). This documents that syntax in the flag's help:+my_task: runmy_taskand everything upstream of itmy_task+: runmy_taskand everything downstream of it+my_task+: bothAdresses #4244
Tests
acceptance/bundle/run/jobs/partial_runcase asserts--only +task_1,task_2+is forwarded unchanged to the run-now request body ("only": ["+task_1", "task_2+"]), proving the documented+syntax is not mangled or rejected client-side.bundle run --helpgolden for the updated--onlydescription.This pull request and its description were written by Isaac.