f7a3815bff
### What this PR does / why we need it?
`ready` label now is used for trigger full e2e test now. If a PR is
ready and merge conflict then, no need to drop the ready label.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
Just a github action change. No need for function test.
- vLLM version: v0.10.2
- vLLM main:
52d0cb8458
Signed-off-by: wangxiyuan <wangxiyuan1007@gmail.com>
21 lines
740 B
YAML
21 lines
740 B
YAML
name: "Merge Conflict Labeler"
|
|
on:
|
|
# So that PRs touching the same files as the push are updated
|
|
push:
|
|
# So that the `dirtyLabel` is removed if conflicts are resolve
|
|
# We recommend `pull_request_target` so that github secrets are available.
|
|
# In `pull_request` we wouldn't be able to change labels of fork PRs
|
|
pull_request_target:
|
|
types: [synchronize]
|
|
|
|
jobs:
|
|
main:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: check if prs are dirty
|
|
uses: eps1lon/actions-label-merge-conflict@v3
|
|
with:
|
|
dirtyLabel: "merge-conflicts"
|
|
repoToken: "${{ secrets.GITHUB_TOKEN }}"
|
|
commentOnDirty: "This pull request has conflicts, please resolve those before we can evaluate the pull request."
|