mirror of
https://github.com/BerriAI/litellm.git
synced 2026-08-28 05:25:59 +00:00
37ca659f84
The unit workflows trigger on pull_request only, so a commit that actually lands on a gated branch ends up with no unit-test check runs at all. The commit status API reports success for those commits, which a release gate reads as "nothing failed" rather than "never tested". PR checks also only ever ran against the merge preview, not the commit that landed, so two branches that are each green can still land broken together Add a push trigger on the two gated branches to the twelve unit workflows and to the code-quality workflow, so every landed commit gets check runs addressable by its SHA test-linting.yml is deliberately left on pull_request only; six of its steps gate on a diff against github.event.pull_request.base.sha, which is empty outside a pull request, and a "what did this branch add" check has no meaning on a merge commit Also key the concurrency group on github.sha and restrict cancel-in-progress to pull_request. The previous group was stable across pushes to a branch, so consecutive merges would cancel the in-flight run for the earlier commit and leave that SHA without a result, which is the same blind spot this change is meant to close
31 lines
691 B
YAML
31 lines
691 B
YAML
name: "Unit Tests: Integrations (Callbacks & Logging)"
|
|
|
|
on:
|
|
pull_request:
|
|
branches:
|
|
- main
|
|
- litellm_internal_staging
|
|
- litellm_oss_staging
|
|
- "litellm_**"
|
|
push:
|
|
branches:
|
|
- main
|
|
- litellm_internal_staging
|
|
|
|
permissions:
|
|
contents: read
|
|
id-token: write
|
|
pull-requests: write
|
|
|
|
concurrency:
|
|
group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.sha }}
|
|
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
|
|
|
|
jobs:
|
|
integrations:
|
|
uses: ./.github/workflows/_test-unit-base.yml
|
|
with:
|
|
test-path: "tests/test_litellm/integrations"
|
|
workers: 2
|
|
reruns: 3
|
|
artifact-name: integrations
|