Read the gamepad from dora-joy, and speak a robot-agnostic contract #2
@@ -35,6 +35,18 @@ jobs:
|
|||||||
- name: Validate the dataflow
|
- name: Validate the dataflow
|
||||||
run: dora validate dataflow.yml
|
run: dora validate dataflow.yml
|
||||||
|
|
||||||
|
# The gamepad dataflow pulls dora-joy by `git:`, but validation resolves
|
||||||
|
# the wiring without fetching it, so this stays offline and still catches
|
||||||
|
# a mistyped port.
|
||||||
|
- name: Validate the gamepad dataflow
|
||||||
|
run: dora validate dataflow-gamepad.yml
|
||||||
|
|
||||||
|
# Same again for the real-arm stack. Its `output_types:` block is what
|
||||||
|
# lets this pass without an arm or a clone of the arm node, so a drift
|
||||||
|
# between it and the tag it pins fails here.
|
||||||
|
- name: Validate the robot dataflow
|
||||||
|
run: dora validate dataflow-robot.yml
|
||||||
|
|
||||||
test:
|
test:
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
steps:
|
steps:
|
||||||
|
|||||||
@@ -12,3 +12,6 @@ build/
|
|||||||
.ruff_cache/
|
.ruff_cache/
|
||||||
out/
|
out/
|
||||||
.dora/
|
.dora/
|
||||||
|
# Where `dora build` clones a `git:` node source, which
|
||||||
|
# dataflow-robot.yml and dataflow-gamepad.yml both have.
|
||||||
|
git/
|
||||||
|
|||||||
Reference in New Issue
Block a user