Skip to content

ci: Run validation jobs in parallel - #2431

Closed
Tim Flannagan (timflannagan) wants to merge 3 commits into
agent-substrate:mainfrom
timflannagan:cleanup/separate-verify-job
Closed

Tim Flannagan (timflannagan) wants to merge 3 commits into
agent-substrate:mainfrom
timflannagan:cleanup/separate-verify-job

Conversation

@timflannagan

@timflannagan Tim Flannagan (timflannagan) commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Run unit tests, repository verification, and linting as separate parallel jobs
so inexpensive failures report without waiting for the test suite.

The workflow uses focused Make targets for linting and non-lint verification,
while make verify remains the comprehensive local entrypoint. The existing
required run-tests check aggregates all three results, so branch protection
and merge-queue behavior remain unchanged.

  • Tests pass
  • Appropriate changes to documentation are included in the PR

Run repository verification and unit tests as independent parallel jobs so
cheap formatting, code generation, and license failures report promptly.

Keep run-tests as an aggregate job over both results to preserve the existing
required status check without a ruleset migration.

Signed-off-by: timflannagan <timflannagan@gmail.com>
Comment thread .github/workflows/pr-workflow.yaml Outdated
Give linting its own Make-backed CI job so it runs in parallel with unit tests
and non-lint verification. Keep the comprehensive make verify command by
composing the focused lint and verification targets.

Include all root and plugin linters behind make lint, and keep the required
run-tests aggregate responsible for every validation result.

Signed-off-by: timflannagan <timflannagan@gmail.com>
@timflannagan Tim Flannagan (timflannagan) changed the title ci: Separate verification from unit tests ci: Run validation jobs in parallel Oct 9, 2026
@timflannagan
Tim Flannagan (timflannagan) marked this pull request as draft October 9, 2026 20:49
Classify formatting and static analysis as linting instead of repository
verification. This puts gofmt, proto formatting, ShellCheck, go vet, and the
Go linters behind the standalone lint target.

Keep verification focused on generated artifacts, module state, licenses,
migrations, metrics, and other repository invariants.

Signed-off-by: timflannagan <timflannagan@gmail.com>
@timflannagan

Copy link
Copy Markdown
Contributor Author

More to unwind, moving to draft while I play around with this more locally

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant