@mumrah do you plan to add tests specifically for the documentation changes?

If the documents have special check or test or have plan for it ,this pr is not needed

Perhaps we can keep the check but skip test

Perhaps we can keep the check but skip test

@chia7712 done with change. to be honest the code is generated by AI with my review. It needs test with this CI and another CI with document change only. you can help to check if the approach make sense now. thanks a lot.

Ideally, we don't need this since the Gradle build cache should avoid running tests if no source files have changed. But we still don't have that working perfectly, so an explicit opt-out of tests seems okay for docs changes.

We should still run the "Compile and Check (Merge Ref)" job since it checks for licenses.

@mumrah thanks for your feedback. at the last. adopt the @chia7712 's suggestion. just ignore the test for document change only. example:
https://github.com/apache/kafka/actions/runs/20434902642

"But we still don't have that working perfectly,"- That's maybe the root cause I see some document only take few time when some other take a very long time.

thanks.

That's maybe the root cause

Yes, very likely. I have an explanation here #18449 (comment)

Essentially, we checkout ${{ github.event.pull_request.head.sha }} which is the HEAD of the PR branch rather than the special "merge ref". This means if a docs PR is far behind trunk, it will get mostly cache misses.

Ideally, we don't need this since the Gradle build cache should avoid running tests if no source files have changed.

That would be the dream 😄 I really hope we can make that happen one day

@chia7712 @mumrah so. does this PR make sense to do?
the dream example: stable within few time:
image

@mumrah @chia7712 @Pankraz76

Thanks for your discussion. I just completed the code refactor and tests. I also add more file types which need to be exclude from tests after the CI test.

It is the final status for me now. If you think it is worthy for this PR. you can help to review. Thanks.

Test 1: Only doc change

Test 2: Only code change

Test 3: Code and Doc changed

BTW. I record some information found in tests here for your reference:

1. "predicate-quantifier: 'every'" will got one warn log but it shouldn't be deleted due to the behavior will be changed accroding to the test result.

_Warning: Unexpected input(s) 'predicate-quantifier', valid inputs are ['token', 'working-directory', 'ref', 'base', 'filters', 'list-files', 'initial-fetch-depth']_

2. ${{ steps.filter.outputs.docs && !steps.filter.outputs.codes }}" is not equal with ${{ steps.filter.outputs.docs == 'true' && steps.filter.outputs.codes == 'false' }}". @Pankraz76 so I rollback part of the code. I also check the plugin example (https://github.com/dorny/paths-filter). you can check my test result here directly.

echo "steps.filter.outputs.docs: ${{ steps.filter.outputs.docs }}"
echo "steps.filter.outputs.codes: ${{ steps.filter.outputs.codes }}"
echo "doc-change-only: ${{ steps.filter.outputs.docs && !steps.filter.outputs.codes }}"
echo "doc-change-only: ${{ steps.filter.outputs.docs == 'true' && steps.filter.outputs.codes == 'false' }}"
the result: true. false. false, true

Thanks !

Regards
Jian