-
-
Notifications
You must be signed in to change notification settings - Fork 840
support WORKING and STAGED in three-dot revisions
#11213
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
Open
elianddb
wants to merge
8
commits into
main
Choose a base branch
from
elian/11204
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 6 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
9e54544
support working and staged in three-dot revisions
elianddb b27ece7
move ref spec resolution onto doltdb
elianddb 692d981
rename and guard the doltdb commit spec resolver
elianddb 178bd57
strengthen three-dot working and staged tests
elianddb ec4376d
document detached head three-dot parity gap
elianddb bae8664
run three-dot diff bats on sql-server
elianddb b461da5
scope working and staged to merge base resolution
elianddb 5361c1f
reject ambiguous three-dot ranges in the cli
elianddb File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm worried this change is overly broad and might result in us treating WORKING or STAGED as HEAD in places we probably shouldn't.
For instance, with this change,
HAS_ANCESTOR('HEAD','WORKING')returns true, even though it shouldn't. I think it's debatable whether or not"STAGED"and"WORKING"should be valid values for theancestorfield here, but they definitely shouldn't be treated as"HEAD"Similarly,
DOLT_DIFF('STAGED...WORKING', ...)now uses HEAD as the merge base and will display already-staged changes in the diff. This seems wrong.I think if the purpose of this function is to generate commits, then it shouldn't accept things that aren't refs to commits.
WORKINGandSTAGEDshould be checked for at a level above this. Perhaps we need a wrapper around the MergeBase logic that accepts these strings.