Problem
This repo currently has no GitHub Actions validation workflow. Recent changes introduced failing tests that were only caught after merge because there was no automatic CI signal on push.
Proposal
Add a validate GitHub Action that runs on:
- pushes to master
- pull requests targeting master
Suggested scope
At minimum, the workflow should:
- set up JDK 17
- cache Maven dependencies
- run the project validation command in a non-publishing mode
A practical starting command is:
- mvn -Dlicense.skip=true -Dfmt.skip=true test
If we want stronger enforcement later, we can decide whether to keep formatting/license steps in CI or split them into a separate workflow after the current build behavior is cleaned up.
Why this matters
- catches test regressions before merge
- provides a visible status check for contributors and maintainers
- reduces the risk of breaking releases due to undetected test failures
Related
Problem
This repo currently has no GitHub Actions validation workflow. Recent changes introduced failing tests that were only caught after merge because there was no automatic CI signal on push.
Proposal
Add a validate GitHub Action that runs on:
Suggested scope
At minimum, the workflow should:
A practical starting command is:
If we want stronger enforcement later, we can decide whether to keep formatting/license steps in CI or split them into a separate workflow after the current build behavior is cleaned up.
Why this matters
Related