-
Notifications
You must be signed in to change notification settings - Fork 639
backend exposes workspace commit merge-failures to frontend #8333
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
… the return value The idea is that top-level merge-conflicts are observable, and we match the diffspecs against them. This allows the frontend to respond to it.
d82bfa6
to
5e65223
Compare
| 'MissingDiffSpecAssociation'; | ||
|
||
export type CreateCommitOutcome = { | ||
newCommit: string; |
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.
Is the newCommit optional still? If so this probably should be newCommit: string | null
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.
That's a great catch! Indeed it is optional, but I forgot to adjust the type.
The rest looks good, so I'll just merge it and make the adaptions on my side |
Thanks again for the changes :) |
The idea is that top-level merge-conflicts are observable, and we match the diffspecs against them. This allows the frontend to respond to it.
Related to #8331.
Tasks