xuxiaowei-com-cn opened a new pull request, #8200: URL: https://github.com/apache/incubator-seata/pull/8200
- [ ] I have read the [CONTRIBUTING.md](https://github.com/apache/incubator-seata/blob/2.x/CONTRIBUTING.md) guidelines. - [ ] I have registered the PR [changes](https://github.com/apache/incubator-seata/tree/2.x/changes). ### Ⅰ. Describe what this PR did Narrow the `pull_request` trigger paths in `.github/workflows/native-namingserver.yml` to reduce unnecessary CI runs. Previously, the workflow was triggered on PR changes across almost all related modules (`build/pom.xml`, `pom.xml`, `common/**`, `console/**`, `namingserver/**`, `test-native-namingserver/**`, `test-native-metadata-merge/**`). Now it only triggers when the workflow file itself or `namingserver/src/main/resources/META-INF/native-image/**` (GraalVM Native Image configuration) is changed. ### Ⅱ. Does this pull request fix one issue? No. ### Ⅲ. Why don't you add test cases (unit test/integration test)? This is a CI workflow configuration change. It does not affect the application code, so no test cases are needed. The correctness can be verified by observing CI trigger behavior. ### Ⅳ. Describe how to verify it 1. PRs that only change non-native-image files (e.g., `common/`, `console/`, `namingserver/src/main/java/`) should **not** trigger the Native Build NamingServer workflow. 2. PRs that change files under `namingserver/src/main/resources/META-INF/native-image/**` should trigger the workflow. 3. PRs that change `.github/workflows/native-namingserver.yml` itself should trigger the workflow. ### Ⅴ. Special notes for reviews This is a CI optimization that reduces resource consumption by avoiding unnecessary native image builds on PRs that don't touch native-image configuration. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
