Skip to content

[automated] Add deterministic CI validation for agentic workflows #20446

Description

@radical

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Agentic workflow source and generated lock files are not guaranteed to receive deterministic compilation and lint validation in pull requests. The repository has focused Infrastructure.Tests contracts, but a PR that changes only .github/workflows/*.md and .github/workflows/*.lock.yml can match the top-level CI skip patterns before those tests run.

There is currently no required CI job that recompiles affected agentic workflows, proves the committed lock files match their Markdown sources, and runs the gh-aw schema and shell linters.

Describe the solution you'd like

Add a dedicated GitHub Actions validation workflow triggered when an agentic workflow Markdown source or generated lock file changes:

paths:
  - '.github/workflows/**/*.md'
  - '.github/workflows/**/*.lock.yml'

The job should install the repository-pinned gh-aw CLI and run deterministic validation such as:

gh aw compile \
  --validate \
  --actionlint \
  --shellcheck \
  --no-check-update

git --no-pager diff --exit-code -- \
  '.github/workflows/*.lock.yml' \
  '.github/workflows/agentics-maintenance*.yml'

It should also run the focused repository contracts:

dotnet test \
  --project tests/Infrastructure.Tests/Infrastructure.Tests.csproj \
  --no-launch-profile -- \
  --filter-class "*.AgenticWorkflowTests" \
  --filter-not-trait "quarantined=true" \
  --filter-not-trait "outerloop=true"

This would fail the PR when:

  • a Markdown source does not compile;
  • a committed lock file is stale;
  • the generated workflow fails GitHub Actions schema validation;
  • generated shell steps fail shellcheck;
  • the generated workflow fails actionlint;
  • repository-specific agentic workflow contracts regress.

Additional context

This job would provide deterministic source-to-lock validation. It would not replace runtime validation for unique action usage shapes such as GitHub App permissions, OIDC, privileged events, or other external service boundaries.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-engineering-systemsinfrastructure helix infra engineering repo stuffneeds-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownerstriage:bot-seenAspire triage bot has seen this issue

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions