jamesnetherton opened a new pull request, #636:
URL: https://github.com/apache/camel-quarkus-examples/pull/636

   Supersedes #627.
   
   * Bumps `eu.maveniverse.maven.scalpel:extension` from 0.4.3 to 0.5.0 (the 
original Dependabot commit, rebased onto `camel-quarkus-main`).
   * Adds `scalpel.excludePaths` to `.mvn/maven.config`.
   
   Scalpel 0.5.0 
([maveniverse/scalpel#229](https://github.com/maveniverse/scalpel/issues/229)) 
treats a changed root-level file that no module owns as a full-build trigger, 
even when modules also changed. The workflow `paths-ignore` only skips CI when 
every changed file matches. So a PR that touches the root `README.adoc` 
together with an example, such as adding a new example, would otherwise test 
every example.
   
   The excludes mirror the workflow `paths-ignore` patterns (`*.adoc`, `*.md`, 
`LICENSE.txt`, `NOTICE.txt`) and add the other non-build repository metadata 
files (`.asf.yaml`, `.gitattributes`, `.gitignore`, `refresh-dockerfiles.sh`). 
Build-relevant root files (`mvnw*`, formatter and license config) still trigger 
a full build.
   
   I checked this locally with a commit that touches the root `README.adoc` and 
`timer-log`. Without the excludes, Scalpel 0.5.0 reported a full build. With 
them, the generated test matrix contains only `timer-log`.
   
   Because this PR changes `.mvn/extensions.xml`, which is a default Scalpel 
full-build trigger, CI will run the full matrix here.
   
   _Claude Code on behalf of James Netherton_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to