fix(ci): use Nu list spread instead of backslash continuations in extract step #7

Merged

David merged 1 commit from fix/workflow-nu-line-continuation into main

2026-05-13 12:53:51 +02:00

David commented

2026-05-13 12:48:56 +02:00

Owner

Summary

The Extract binary from build step in .forgejo/workflows/build-oci-image.yml invoked ^docker buildx build with bash-style backslash + newline line continuations. Nushell does not interpret trailing \ as a line continuation, so the parser saw the next line as a fresh statement and bailed with nu::parser::parse_mismatch: expected operator at --target export.

Rebuild the step using the same Nu-list spread pattern the adjacent Build and push step already uses: collect the three --build-arg flags into a list, then call ^docker buildx build --target export --output ... ...$build_args -f oci-build/Dockerfile . on a single logical line.

Docs reference: Nushell pipeline / continuation rules: https://www.nushell.sh/book/pipelines.html. (There is no \-style continuation; Nu continues lines implicitly inside list/record/parenthesis literals.)

Test plan

nu parses the new list locally with dummy env vars set; output is the expected six-element list.
Re-run .forgejo/workflows/build-oci-image.yml; the Extract binary from build step now reaches docker buildx build and produces ./output/youtrack-cli.

## Summary The `Extract binary from build` step in `.forgejo/workflows/build-oci-image.yml` invoked `^docker buildx build` with bash-style backslash + newline line continuations. Nushell does not interpret trailing `\` as a line continuation, so the parser saw the next line as a fresh statement and bailed with `nu::parser::parse_mismatch: expected operator` at `--target export`. Rebuild the step using the same Nu-list spread pattern the adjacent `Build and push` step already uses: collect the three `--build-arg` flags into a list, then call `^docker buildx build --target export --output ... ...$build_args -f oci-build/Dockerfile .` on a single logical line. Docs reference: Nushell pipeline / continuation rules: <https://www.nushell.sh/book/pipelines.html>. (There is no `\`-style continuation; Nu continues lines implicitly inside list/record/parenthesis literals.) ## Test plan - [x] `nu` parses the new list locally with dummy env vars set; output is the expected six-element list. - [ ] Re-run `.forgejo/workflows/build-oci-image.yml`; the `Extract binary from build` step now reaches `docker buildx build` and produces `./output/youtrack-cli`.

David added 1 commit

2026-05-13 12:48:56 +02:00

fix(ci): use Nu list spread instead of backslash continuations in extract step

Check / fmt + clippy + build + tests (pull_request) Successful in 6s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

af4d0d2676

Nushell does not treat trailing-backslash + newline as line continuation, so the `^docker buildx build \ ...` block in the "Extract binary from build" step failed at parse time with `expected operator` on the second flag. Rebuild it the same way the "Build and push" step does: collect the `--build-arg` triplet into a Nu list, then call `^docker buildx build ... ...$build_args ...` on a single logical line. Behavior is unchanged; the command parses now.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>