Duansg opened a new pull request, #6432:
URL: https://github.com/apache/shenyu/pull/6432
### What changes are proposed in this pull request?
None of the CI/test workflows declare a `concurrency` group, so pushing new
commits to a PR — or merging several PRs in quick succession — leaves earlier
runs going and wastes hours of runner time on stale commits.
This adds a top-level concurrency block to the 6 CI/test workflows:
concurrency:
group: ${{ github.workflow }}-${{ github.event.pull_request.number ||
github.ref }}
cancel-in-progress: true
Workflows changed: `ci`, `e2e`, `it`, `it-k8s`, `k8s-examples-http`,
`CodeQL`.
Intentionally NOT touched — `docker-publish` / `docker-publish-dockerhub`:
release tasks have no concurrency group, so an in-flight image push is never
cancelled. `auto-notify` / `issue-label` are excluded too (not builds).
Trade-off: during a burst of master merges only the tip is fully re-tested;
intermediate commits lose their own CI record. Release/publish integrity is
unaffected.
Ref:
https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency
### How was this patch tested?
CI only (workflow config). All 6 files validated as parsable YAML.
- [x] You have read the [contribution
guidelines](https://shenyu.apache.org/community/contributor-guide).
- [ ] You submit test cases (unit or integration tests) that back your
changes.
- [ ] Your local test passed `./mvnw clean install
-Dmaven.javadoc.skip=true`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
