Skip to content

chore/ci: bump actions/checkout from v1 to v7.0.1 - #487

Open
marcleblanc2 wants to merge 1 commit into
mainfrom
marc/bump-actions-checkout-v7
Open

marcleblanc2 wants to merge 1 commit into
mainfrom
marc/bump-actions-checkout-v7

Conversation

@marcleblanc2

Copy link
Copy Markdown
Contributor

Why

The SCIP workflow pinned actions/checkout@50fbc622fc4ef5163becd7fab6573eac35f8462e, which is v1 from November 2019 (the old runner-plugin implementation). Its fetch-depth defaults to no limit, so every push fetched every branch and tag (~17.5k objects), and it fetches refs/heads/* rather than the commit under test.

That caused this failure on #486: the branch was force-pushed one second after the first push, the fetch picked up the new tip only, and checkout of the original commit died with fatal: unable to read tree.

What

Bump to actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1, the current release.

  • Defaults to fetch-depth: 1, so the job clones shallow.
  • Fetches the exact github.sha, which GitHub still serves after a force-push, so the race goes away.

scip-go and src code-intel upload only need the working tree and git rev-parse HEAD; neither needs history.

Test plan

The SCIP workflow runs on push to this branch; confirm the checkout step logs --depth=1 and the job passes.

The pinned SHA was actions/checkout v1 (Nov 2019), which defaults to an
unlimited fetch depth and fetches refs/heads/* instead of the commit under
test. A force-push seconds after the first push left the fetched refs
without the original commit, and checkout failed with
"fatal: unable to read tree".

v7.0.1 defaults to fetch-depth 1 and fetches the exact commit SHA, so the
SCIP job clones shallow and survives a force-push race.

Amp-Thread-ID: https://ampcode.com/threads/T-01a0cc21-4b1a-74dd-aa9f-8d1abc501c9a
Co-authored-by: Amp <amp@ampcode.com>
@marcleblanc2
marcleblanc2 requested a review from a team September 23, 2026 02:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants