From fbabcc2022dbbe214716651f6a628a0f6f96c0af Mon Sep 17 00:00:00 2001 From: PJ Reiniger Date: Wed, 19 Nov 2025 00:30:26 -0500 Subject: [PATCH] [ci] Run robotpy gen steps in series instead of simultaneously (#8404) The update yaml step _might_ cause changes that would affect the build file generation. Since `bazel run //:write_robotpy_update_yaml_files` runs them all at once, user that was using the github action to fix their python stuff would end up having to run it twice. By running the steps individually in series, this should be able to get it in one swoop. --- .github/workflows/bazel.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/bazel.yml b/.github/workflows/bazel.yml index a8e7b5736e..66129691c9 100644 --- a/.github/workflows/bazel.yml +++ b/.github/workflows/bazel.yml @@ -135,8 +135,11 @@ jobs: run: bazel test //... -k --test_tag_filters=robotpy_scan_headers --build_tests_only shell: bash - - name: Run robotpy pregeneration - run: bazel run //:write_robotpy_files + - name: Run yaml file generation + run: bazel run //:write_robotpy_update_yaml_files + + - name: Run build file generation + run: bazel run //:write_robotpy_generated_pybind_files - name: Check Output run: git --no-pager diff --exit-code HEAD