ci(cann): drop auto-triggers (workflow has zero jobs upstream)#80
Open
marksverdhei wants to merge 1 commit into
Open
ci(cann): drop auto-triggers (workflow has zero jobs upstream)#80marksverdhei wants to merge 1 commit into
marksverdhei wants to merge 1 commit into
Conversation
Same pattern as PR #74 (build-sycl.yml): upstream PR ggml-org#23705 commented out every job in this workflow, but the push:master + pull_request auto-triggers stayed live. Any PR touching ggml/src/ggml-cann/** would create a zero-job "failure" run. Keep workflow_dispatch so the workflow stays available for manual runs once jobs are re-enabled (which requires provisioning dedicated runners per the upstream TODO).
This was referenced Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Same pattern as PR #74 —
build-cann.ymlhas had every job commented out since upstream PR ggml-org#23705, but kept itspush:master+pull_requestauto-triggers. Any PR touchingggml/src/ggml-cann/**would produce a zero-job "failure" run on this workflow.This PR strips those auto-triggers and keeps only
workflow_dispatch, so the workflow can still be invoked manually if/when jobs are re-enabled.Why this hasn't fired yet on ht
Unlike
build-sycl.yml(which has a path filter that matches almost any C/C++ change), the CANN pull_request path filter is narrow:ggml/src/ggml-cann/**. No recent PR has touched those files, so the zero-job failure runs haven't materialized. They will the next time a contributor touches CANN code.Test plan
Related
🤖 Generated with Claude Code