Repository navigation
ci: one status workflow so the README can carry a single CI badge - #1457
Merged
Merged
Conversation
elibol
requested review from
binarybana,
cryos,
kkraus14,
nihalpasham,
roivanov and
rparolin
as code owners
October 8, 2026 16:36
elibol
marked this pull request as draft
October 8, 2026 17:03
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
roivanov
previously approved these changes
Oct 8, 2026
cryos
previously approved these changes
Oct 8, 2026
elibol
added a commit
that referenced
this pull request
Oct 8, 2026
…oot CI badges (#1395) Companion to #1394: the references outside `cutile-rs/` that still pointed at the old NVlabs/cutile-rs home. - `repository` field of cuda-bindings, cuda-core, cuda-core-derive, and cuda-async (crates.io and docs.rs read it). - cuda-oxide glossary, VMM page, cuda-host README, scaffold template, and doctor comments now say the shared host crates live at the repository root; the four rows in `dependency-licenses.csv` record them as 0.4.0 path dependencies instead of 0.3.1 from crates.io. - Root README gets CI badges, one per pipeline, plus a docs badge. A single combined badge is proposed separately in #1457. The cuda-oxide book builds warning-free, and the source-reference, host-API-path, and pin-parity guards pass. --------- Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com> Co-authored-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Badges are per workflow file, and the SIMT and Tile pipelines have to stay separate for now: ci.yml runs on GitHub-hosted runners on push and pull_request, while cutile-rs.yml runs on NVIDIA self-hosted runners and can only trigger on push to main and the copy-pr-bot mirror branches. So the README ends up with one badge per pipeline unless something combines them. ci-status.yml runs whenever either pipeline completes on main, finds the newest completed push run of each that actually executed jobs, and fails if that run failed. A run whose jobs were all skipped (the cutile-rs.yml `changes` gate on a non-Tile push) and a cancelled run are skipped over, because taking either at face value would turn the badge green while the last real run was red. The README badge points at this workflow. Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
elibol
marked this pull request as ready for review
October 8, 2026 18:04
elibol
force-pushed
the
ci/combined-status-badge
branch
from
October 8, 2026 18:04
ba4be26 to
2941b5b
Compare
Same shape as the component READMEs, which open with a centered badge block above a left-aligned heading. Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Same look as the cutile-rs badges: default style, short labels, no logos. Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
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
3 participants
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.
Stacked on #1395; only the last commit is new, and the diff shrinks to it once #1395 merges.
Badges are per workflow file, and the SIMT and Tile pipelines have to stay separate (the Tile lanes run on self-hosted runners and cannot trigger on pull_request), so the root README ends up with two CI badges.
ci-status.ymlruns wheneverCIorcutile-rs-prcompletes onmain, takes the newest completed push run of each pipeline that actually executed jobs, and fails if either failed. The README then carries one CI badge pointing at it.Runs whose jobs were all skipped (the Tile
changesgate on a non-Tile push) and cancelled runs are skipped over, so a later no-op run cannot turn the badge green while the last real run was red. The logic was dry-run against this repo's run history. The badge reads "no status" until the first run after merge.The badge row is centered, matching the component READMEs.