Files
lukaszraczylo 45b650410d ci: run yaegi-check and the pricing-sync tests on pull requests
A go test run over ./... stops at nested modules, so CI never ran
tools/pricing-sync or the Yaegi interpreter check. A new job runs both
with Go 1.25.x. The go.sum of tools/yaegi-check now holds its test
dependencies, and its go.mod lists the prometheus modules as direct
dependencies. The .gitattributes comment now says that the
export-ignore rules for tools/, webui/, examples/ and testdata/ do take
effect.

Claude-Session: https://claude.ai/code/session_01V5jYJNxpDFdJkyyExpADrv
2026-09-23 09:44:32 +01:00

51 lines
1.3 KiB
YAML

name: Pull Request
on:
pull_request:
branches:
- main
push:
branches:
- "**"
- "!main"
permissions:
contents: read
pull-requests: write
security-events: write
jobs:
pr-checks:
uses: lukaszraczylo/shared-actions/.github/workflows/go-pr.yaml@main
with:
go-version: "1.25.x"
coverage-threshold: 75
secrets: inherit
# C2 (review round 3, 2026-09): the shared pr-checks job above runs
# `go vet`/staticcheck/`go test -race`/gosec/govulncheck/CodeQL against
# `./...`, which stops at every NESTED go.mod (tools/yaegi-check,
# tools/pricing-sync, integration/) — so neither the yaegi interpreter
# compatibility check nor the pricing-sync tool's own tests ran in CI at
# all before this job existed. This job runs both, the same two commands
# a contributor is expected to run locally before pushing.
yaegi-and-tools:
name: Yaegi compatibility & tooling
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- name: Checkout
uses: actions/checkout@v6
- name: Setup Go
uses: actions/setup-go@v6
with:
go-version: "1.25.x"
cache: true
- name: yaegi-check
run: make yaegi-check
- name: pricing-sync tests
run: cd tools/pricing-sync && go test ./...