mirror of
https://github.com/zama-ai/tfhe-rs.git
synced 2026-01-10 07:08:03 -05:00
chore(ci): always run should-run step against base commit
Running against last remote commit would induce undesired behavior, especially on pull-request approval. For example a change in integer layer could occur in the pull-request commits list but the changes aren't contained in the last remote commit. Then, on approval, aws_tfhe_integer_tests.yml workflow would be skipped although it should run regarding the base commit.
This commit is contained in:
@@ -54,7 +54,6 @@ jobs:
|
||||
id: changed-files
|
||||
uses: tj-actions/changed-files@d6e91a2266cdb9d62096cebf1e8546899c6aa18f
|
||||
with:
|
||||
since_last_remote_commit: true
|
||||
files_yaml: |
|
||||
gpu:
|
||||
- tfhe/Cargo.toml
|
||||
|
||||
Reference in New Issue
Block a user