Skip to content

Comments

allow triggering the upstream-dev CI if the check is skipped#11184

Merged
keewis merged 3 commits intomainfrom
nightly-ci
Feb 20, 2026
Merged

allow triggering the upstream-dev CI if the check is skipped#11184
keewis merged 3 commits intomainfrom
nightly-ci

Conversation

@keewis
Copy link
Collaborator

@keewis keewis commented Feb 20, 2026

#11096 inadvertently skipped CI if the detect-ci-trigger job was skipped. By replacing the default success() (true only if all previous steps reported 'success', everything else, including 'skipped', will evaluate to false) with always() and comparing against the result of the cache-pixi-lock step, we can get CI to run on workflow_dispatch and schedule events again.

This has caused me to believe we don't have any current issues with upstream, when we actually do have breaking tests, see #11183.

cc @doronbehar

@github-actions github-actions bot added the Automation Github bots, testing workflows, release automation label Feb 20, 2026
@keewis
Copy link
Collaborator Author

keewis commented Feb 20, 2026

This appears to have worked, see https://github.com/pydata/xarray/actions/runs/22229189964/job/64303881012

@keewis keewis enabled auto-merge (squash) February 20, 2026 15:16
@keewis keewis merged commit 5e31466 into main Feb 20, 2026
42 of 43 checks passed
@keewis keewis deleted the nightly-ci branch February 20, 2026 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Automation Github bots, testing workflows, release automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant