Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use treeless clone to efficiently retrieve enough history to diff with the --merge-base option. #34

Merged
merged 1 commit into from
Jan 1, 2024

Conversation

lerebear
Copy link
Owner

Closes #31.

@lerebear lerebear force-pushed the lerebear-deepen-history branch 8 times, most recently from bcf310b to 354ab13 Compare December 31, 2023 07:49
@lerebear lerebear changed the title Find merge base by progressively deepening history. Use treeless clone to efficiently retrieve enough history to diff with the --merge-base option. Dec 31, 2023
@lerebear lerebear force-pushed the lerebear-deepen-history branch 7 times, most recently from e3f8d5b to 385b768 Compare December 31, 2023 22:33
A treeless clone contains all git history (and so can always find the
correct merge base), but is more efficient than a normal clone/fetch.

In order to use both treeless clone and fetch operations, we now manage
git clone, fetch and checkout operations ourselves rather than relying
on actions/checkout.
@lerebear lerebear force-pushed the lerebear-deepen-history branch from 385b768 to a4fcbe2 Compare January 1, 2024 04:18
@lerebear lerebear marked this pull request as ready for review January 1, 2024 04:19
@lerebear lerebear merged commit 352c83a into main Jan 1, 2024
2 checks passed
@lerebear lerebear deleted the lerebear-deepen-history branch January 1, 2024 04:20
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.

Workflow occasionally fails with "no merge base" error
1 participant