Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ci): always run should-run step against base commit #2034

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

soonum
Copy link
Contributor

@soonum soonum commented Feb 7, 2025

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.

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.
@soonum soonum added the ci label Feb 7, 2025
@soonum soonum requested a review from IceTDrinker February 7, 2025 13:57
@soonum soonum self-assigned this Feb 7, 2025
@cla-bot cla-bot bot added the cla-signed label Feb 7, 2025
@soonum soonum merged commit 01aa7d1 into main Feb 10, 2025
303 of 326 checks passed
@soonum soonum deleted the dt/ci/should_run_base_commit branch February 10, 2025 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants