mengzhx/deepseek-harness
1
0
Fork 0
mirror of https://github.com/deepseek-ai/deepseek-harness.git synced 2026-08-29 04:26:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(pre-push-checks): diagnose absent CI runs as a merge conflict

Browse Source 
A CONFLICTING PR gets no pull_request workflow runs, so `gh pr checks`
reports "no checks reported" and the runs API returns total_count 0. That
looks like a dropped GitHub event, and the reflex fixes for one — empty
commits, draft/ready toggles, revert-and-restore bounces — all leave the
count at zero while adding junk history to the branch.

Record the mergeability check as the first diagnostic step, name the
conflict as the cause, and point at `git merge-tree` for the conflicting
paths.
This commit is contained in:
Chinesezjc
2026-08-11 15:46:24 +08:00
parent ea1b494614
commit 26bcff8ab4
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/dsh-pre-push-checks/SKILL.md
+8
View File
@@ -112,4 +112,12 @@ gh pr checks
Report pending checks as pending. Inspect failures before attributing them to the branch or the environment.
When `gh pr checks` reports "no checks reported" and `/actions/runs?head_sha=<sha>` returns `total_count: 0`, read mergeability before suspecting the push or a dropped GitHub event:
```sh
gh pr view <number> --json mergeable,mergeStateStatus
```
GitHub creates no `pull_request` workflow runs while a PR is `CONFLICTING`/`DIRTY`, so the absent signal is the conflict, not infrastructure. Resolving the conflict is the only fix; empty commits, `--allow-empty` pushes, draft/ready toggles, and revert-and-restore bounces all leave `total_count` at zero and add junk history. Confirm the conflicting paths with `git merge-tree --write-tree HEAD origin/<base>` when the branch cannot be merged locally yet.
For `gh stack sync`, use the post-sync validation sequence instead of pretending the ordinary order was possible.