alamb commented on PR #11097: URL: https://github.com/apache/arrow-rs/pull/11097#issuecomment-5833455256
> i suppose we will go with this approach if the paths-filter isnt feasible; the amount of python code is manageable. my main concern is im a bit confused by how the routing logic is separated I still don't understand the need for python code at all It seems to me ideally what we would do is: 1. Run some subset of the CI tests on PRs 2. Run all the CI tests in the merge queue 3. Don't run CI tests explicitly on push to master (as they already run on the same commit in the merge queue) -- 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]
