#6999 [V2] Add GitHub Actions workflow for Go unit tests Pull request opened by pingsutw Why are the changes needed? The Flyte repository currently has no CI workflow for running Go unit tests. There's

check-generate.yml

for generated file validation and

build-ci-image.yml

for Docker image builds, but no actual test execution on PRs. What changes were proposed in this pull request? Add a new GitHub Actions workflow (

.github/workflows/go-tests.yml

) that runs Go unit tests across all 9 components in parallel using a matrix strategy: | Component | Test Files | Notes | | ------------ | ---------- | -------------------------------------- | | flyteplugins | 88 | Standard go test | | flytestdlib | 74 | Standard go test | | runs | 12 | Excludes test/ dir (integration tests) | | executor | 6 | Needs envtest for controller tests | | flytecopilot | 5 | Standard go test | | dataproxy | 3 | Standard go test | | flyteidl2 | 2 | Standard go test | | actions | 2 | Standard go test | | manager | 1 | Standard go test | Key design decisions: • Uses

actions/setup-go@v5

with Go 1.24 (matching

go.mod

) instead of the Docker CI image • Race detector and coverage enabled for all components • Envtest setup for executor controller tests (version pinned to controller-runtime dependency) • Integration/e2e tests excluded (runs/test, executor/e2e) • Concurrency control to cancel superseded runs on the same PR How was this patch tested? • YAML syntax validated • Verified all 9 component directories exist and contain the expected number of test files • Envtest setup matches the pattern used in

executor/Makefile

Labels • added: New CI workflow for Go unit tests Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. •

main

• #6583 • #6999 👈 flyteorg/flyte