The Modernization Tool already publishes release assets on version tags, so storing an additional Actions artifact for every development build is unnecessary. This keeps pre-merge and release validation while minimizing Actions artifact storage.
Scope
CI workflow only. No installer/runtime code, payload ownership, Modernization behavior, or release asset format is changed.
## Summary
- run syntax and unit tests only for direct pushes to `test/**`
- keep a real Windows EXE/ZIP build on pull requests, `main`, version tags, and manual runs
- stop storing automatic test artifacts on PRs and normal `main` pushes
- create a 7-day Actions artifact only for explicit manual runs
- keep tag-based GitHub Release publishing unchanged
- cancel superseded runs for the same event/ref
## Why
The Modernization Tool already publishes release assets on version tags, so storing an additional Actions artifact for every development build is unnecessary. This keeps pre-merge and release validation while minimizing Actions artifact storage.
## Scope
CI workflow only. No installer/runtime code, payload ownership, Modernization behavior, or release asset format is changed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
test/**main, version tags, and manual runsmainpushesWhy
The Modernization Tool already publishes release assets on version tags, so storing an additional Actions artifact for every development build is unnecessary. This keeps pre-merge and release validation while minimizing Actions artifact storage.
Scope
CI workflow only. No installer/runtime code, payload ownership, Modernization behavior, or release asset format is changed.