Make fetching source tarball by git commit more robust #4680
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(created using
eb --new-pr
)I had a crate that was supposed to fetch a git commit from https://github.com/astral-sh/pubgrub. However the specified git commit
21ceec9a5fd2e8d6f71c3ea2999078fecbd13cbe
was not available forgit checkout
after the clone.My understanding is, that this commit is not reachable from the default (main) branch that is fetched, possibly after same rebase.
The approach done here is to add a separate
git fetch
call to fetch the specified commit. That resolves the issue in my case.We could go even further and don't use
git clone
at all: