Skip to content
This repository was archived by the owner on Sep 20, 2026. It is now read-only.

Actions: spin-stack/spinbox

Actions

CI

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
ci.yml
1,002 workflow runs
1,002 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
The proto lint policy is spin's, not a second opinion CI #1013: Commit e0950a0 pushed by aledbf
2m 45s main
main
2m 45s
A workspace runs with no containerd CI #1012: Commit 0f78339 pushed by aledbf
2m 49s main
main
2m 49s
Lint the protos, and pay what STANDARD costs CI #1011: Commit e9c98b7 pushed by aledbf
3m 23s main
main
3m 23s
Do not wait for a lock this process's parent is holding CI #1010: Commit de1a4e9 pushed by aledbf
2m 38s main
main
2m 38s
One lock, two users: open it read-only CI #1009: Commit e949a45 pushed by aledbf
12m 35s main
main
12m 35s
The lock goes where a real bash runs, not in the Taskfile CI #1008: Commit c73ca0a pushed by aledbf
43s main
main
43s
Whatever boots VMs on this host takes one lock CI #1007: Commit fbd2c41 pushed by aledbf
1m 26s main
main
1m 26s
Documentation that named files this tree no longer has CI #1006: Commit 68dda91 pushed by aledbf
2m 47s main
main
2m 47s
The chain tests belong in the lane that has a machine CI #1005: Commit b5cf1d5 pushed by aledbf
1m 43s main
main
1m 43s
The launcher reads the pointer instead of remembering a path CI #1004: Commit c79f8ba pushed by aledbf
27s main
main
27s
A guest boots from the chain, and the base image survives it CI #1003: Commit 777ddc6 pushed by aledbf
23s main
main
23s
A VM's disk is a qcow2 chain over the release's base image CI #1002: Commit 78f2050 pushed by aledbf
45s main
main
45s
api/CLAUDE.md described two RPCs that no longer exist CI #1001: Commit b34c272 pushed by aledbf
4m 36s main
main
4m 36s
Delete the memory online/offline RPCs CI #1000: Commit 8ac2502 pushed by aledbf
2m 34s main
main
2m 34s
CI runs once, and never cancels a commit on main CI #999: Commit 6be13dd pushed by aledbf
4m 28s main
main
4m 28s
CI runs once, and never cancels a commit on main CI #998: Pull request #83 opened by aledbf
2m 55s ci/run-once-never-cancel-main
ci/run-once-never-cancel-main
2m 55s
Move the tarball pin to the release cut from the commit go.mod names CI #997: Commit fc2e2e0 pushed by aledbf
2m 31s chore/pin-machine-at-main
chore/pin-machine-at-main
2m 31s
Pin the machine at main, not at a branch that has been merged away CI #996: Commit da446fa pushed by aledbf
3m 14s main
main
3m 14s
Pin the machine at main, not at a branch that has been merged away CI #995: Pull request #82 opened by aledbf
35s chore/pin-machine-at-main
chore/pin-machine-at-main
35s
Pin the machine at main, not at a branch that has been merged away CI #994: Commit 17290f5 pushed by aledbf
2m 33s chore/pin-machine-at-main
chore/pin-machine-at-main
2m 33s
Type-check the tagged tests, which nothing was doing CI #993: Commit e3405dc pushed by aledbf
1m 21s main
main
1m 21s
One definition of the machine, imported instead of spelled again CI #992: Pull request #81 synchronize by aledbf
2m 34s feat/one-machine-definition
feat/one-machine-definition
2m 34s
Type-check the tagged tests, which nothing was doing CI #991: Commit 486c468 pushed by aledbf
2m 30s feat/one-machine-definition
feat/one-machine-definition
2m 30s
One definition of the machine, imported instead of spelled again CI #990: Pull request #81 synchronize by aledbf
2m 29s feat/one-machine-definition
feat/one-machine-definition
2m 29s
The disk format is stated by whoever has the disk, not guessed and no… CI #989: Commit dcade02 pushed by aledbf
8s feat/one-machine-definition
feat/one-machine-definition
8s