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:
David Testé
2025-02-07 14:56:14 +01:00
committed by David Testé
parent 73412a43bf
commit 01aa7d105c
17 changed files with 0 additions and 17 deletions

View File

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