molecule-ai/molecule-core
35
0
Fork 2
Code Issues 16 Pull Requests 2 Actions 49 Packages Projects Releases Wiki Activity

Merge pull request #2379 from Molecule-AI/auto/fix-migration-collision-fetch-depth

Browse Source 
fix(ci): drop --depth=1 from migration collision check fetch
This commit is contained in:
Hongming Wang 2026-04-30 13:31:53 +00:00 committed by GitHub
commit 4d1156cb8b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
.github/workflows/check-migration-collisions.yml vendored
View File

@ -44,8 +44,15 @@ jobs:
# gh CLI uses GH_TOKEN from env
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
# Make sure base ref is fetched (checkout@v4 with fetch-depth=0
# fetches history but not necessarily named refs in the form we
# expect; explicit fetch is cheap insurance).
git fetch origin "${{ github.event.pull_request.base.ref }}" --depth=1 || true
# Ensure the named base ref exists locally. checkout@v4 with
# fetch-depth=0 pulls full history, but the explicit fetch is
# cheap insurance against form-of-ref differences across runs.
#
# IMPORTANT: do NOT pass --depth=1 here. The script below uses
# `git diff origin/<base>...<head>` (three-dot, merge-base form),
# which fails with "fatal: no merge base" if the base ref is
# shallow. The auto-promote staging→main PR (#2361) was blocked
# by exactly this for ~5h on 2026-04-30 — the depth=1 fetch
# overwrote checkout@v4's full-history clone with a shallow tip.
git fetch origin "${{ github.event.pull_request.base.ref }}" || true
python3 scripts/ops/check_migration_collisions.py