Skip to content

tests-via-crave: limit paths#4449

Merged
dsmiley merged 1 commit into
apache:mainfrom
dsmiley:tests-via-crave-path-filter
May 19, 2026
Merged

tests-via-crave: limit paths#4449
dsmiley merged 1 commit into
apache:mainfrom
dsmiley:tests-via-crave-path-filter

Conversation

@dsmiley
Copy link
Copy Markdown
Contributor

@dsmiley dsmiley commented May 19, 2026

Don't want to run Crave for PRs that merely touch the changelog or for some other things.

@dsmiley dsmiley requested a review from janhoy May 19, 2026 13:38
- '*'
paths:
- 'solr/**/src/**'
- 'gradle/libs.versions.toml'
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shuold changes to the broader gradle build files also trigger a full test

Copy link
Copy Markdown
Contributor

@janhoy janhoy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Not sure about gradle/** - but the precommit tests are probably enough to catch bugs that might be introduced in the build?

@dsmiley dsmiley merged commit b0dd510 into apache:main May 19, 2026
3 of 4 checks passed
@dsmiley dsmiley deleted the tests-via-crave-path-filter branch May 19, 2026 20:40
@dsmiley
Copy link
Copy Markdown
Contributor Author

dsmiley commented May 19, 2026

It's of course possible to imagine changes that wouldn't trigger this workflow that could cause a test to fail (e.g. certain gradle/build changes relating to tests) but I think this is fine & simple. We can always change it later if we grow dissatisfied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants