Open aderk opened 3 months ago
Can confirm that this is still a problem. Switching to file context is a workaround that removes this error.
@aderk Sorry for the delay, do you have a link to your repo? Are you using submodules?
#1 0.051 fatal: Not a valid object name SHA^{commit}
Also this message should not fail your build and still fetch correctly per https://github.com/moby/buildkit/issues/2888.
Contributing guidelines
I've found a bug, and:
Description
build-push-action@v5.3.0 fails to get the ref during
on: push:
trigger (on: pull_request:
works as expected). It then falls back to downloading cloning the entire repo (slow).Succinctly,
build-push-action@v5.3.0
succeeds with refs of the formhttps://github.com/OWNER_NAME/REPO_NAME.git#refs/pull/PULL_NUMBER/merge
and fails (with fallback to full clone) with the formhttps://github.com/OWNER_NAME/REPO_NAME.git#SHA
Expected behaviour
Only the ref w/ depth=1 is fetched (fast) as with
on: pull_request:
triggers.Actual behaviour
The whole repo is cloned (slow). In my case it takes 8m instead of 1m
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
No response
Additional info
https://github.com/docker/build-push-action/issues/638 is somewhat similar, in that the initial error log line is identical
fatal: Not a valid object name