-
Notifications
You must be signed in to change notification settings - Fork 624
graph -> stacks: conformity #9209
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
Merged
Merged
Conversation
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@Byron is attempting to deploy a commit to the GitButler Team on Vercel. A member of the Team first needs to authorize it. |
6c17155
to
ce052a6
Compare
ce052a6
to
3c8c05b
Compare
3c8c05b
to
d840bb8
Compare
d840bb8
to
fd3c8db
Compare
That way searches through all nodes can be avoided just to find a segment with a spsecific ref-name.
Later this will allow assuring the the local tracking branch of the target ref will always be connected with the workspace graph, which should in turn assure we can show the integrated (but still visible from forkpoint) segments correctly.
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.
Bring the new Graph based backend for workspaces to conformity with the existing implementation - it shouldn't be worse, but ideally can be the daily driver for
ws3
users.Tasks
ref_info2
workspace should never be ignored (i.e. find workspace, but set entrypoint, or start at workspace and extract what's needed)integrated_tips_stop_early
)'archived' out-of-workspace refs are forcefully added (and marked) accordingly- archived segments can still be used for reconcilation if they are reachable, it's really about the frontend having this data even after a workspace updatetwo_dependent_branches_first_rebased_and_merged_into_target
)Not to forget
archived
flagRelated
Previous