sdods run -p demo-shop --process pr-chek✖ CONFIG_NOT_FOUND: Process "pr-chek" is not defined for project demo-shop.
hint: Known processes: pr-check, nightly-regression, release-gate, api-contract. Define it under processes: in sdods.project.yaml or defaults.processes in sdods.workspace.yaml.Typo, obviously. But the hint mentions two files — how do those two lists combine? We have pr-check in both.
Accepted answer
By name, project last.
The workspace defaults.processes are collected first, then the project's own processes: are applied over them. Same name replaces outright; a new name is added. So a pr-check in the project file is the whole of the pr-check you get, and the workspace one contributes nothing to it — not even the fields the project omitted.
That is the array-replace rule again, applied per entry rather than per list.
sdods processes list -p demo-shopThat prints the merged result: name, trigger, tags, layers, browsers, env, gates and schedule, which is what a run with --process will actually use.
And explicit flags beat the process. --process nightly-regression -b chromium runs the nightly tag expression on one browser rather than three, which is handy for reproducing a nightly failure locally without editing the yaml.
Have a different question? Ask it.