llama-stack-mirror/.github/actions
Ashwin Bharambe fdb144f009
revert: feat(ci): use @next branch from llama-stack-client (#3593)
Reverts llamastack/llama-stack#3576

When I edit Stainless and codegen succeeds, the `next` branch is updated
directly. It provides us no chance to see if there might be something
unideal going on. If something is wrong, all CI will start breaking
immediately. This is not ideal. I will likely create another staging
branch `next-release` or something to accomodate the special workflow
that Stainless requires.
2025-09-29 10:41:04 -07:00
..
run-and-record-tests feat(tests): migrate to global "setups" system for test configuration (#3390) 2025-09-09 15:50:56 -07:00
setup-ollama feat(tests): migrate to global "setups" system for test configuration (#3390) 2025-09-09 15:50:56 -07:00
setup-runner revert: feat(ci): use @next branch from llama-stack-client (#3593) 2025-09-29 10:41:04 -07:00
setup-test-environment revert: feat(ci): use @next branch from llama-stack-client (#3593) 2025-09-29 10:41:04 -07:00
setup-vllm test: Add VLLM provider support to integration tests (#2757) 2025-07-24 09:42:26 -07:00