Add message when pulling to indicate from and to causal hashes.#5870
Merged
ChrisPenner merged 3 commits intotrunkfrom Sep 11, 2025
Merged
Add message when pulling to indicate from and to causal hashes.#5870ChrisPenner merged 3 commits intotrunkfrom
ChrisPenner merged 3 commits intotrunkfrom
Conversation
aryairani
approved these changes
Sep 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
Adds a message indicating where we're pulling from/to,
this will be helpful for cases where pulls are feeling really slow, I can investigate them more easily.
cc @pchiusano
Implementation notes
When pulling on a branch, show the old and new causal hashes.
Interesting/controversial decisions
Probably not the best that we need to do this at all, but more visibility into what's happening isn't a bad thing, and it makes it easy for users to
reset #oldif they want to undo a pull.Test coverage
I tried it out