Skip to content

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

Merged
merged 2 commits into from
Apr 29, 2025

Conversation

Byron
Copy link
Collaborator

@Byron Byron commented Apr 29, 2025

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

  • reproduce
  • backend exposes a new rejection reason with diffspecs for merge failure
  • frontend type is aware of rejection reasons

Copy link

vercel bot commented Apr 29, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
gitbutler-components ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 29, 2025 7:09pm
gitbutler-web ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 29, 2025 7:09pm

@vercel vercel bot temporarily deployed to Preview – gitbutler-web April 29, 2025 13:52 Inactive
@vercel vercel bot temporarily deployed to Preview – gitbutler-components April 29, 2025 13:52 Inactive
@Byron Byron changed the title groundworks for handling merge-commit failures backend exposes workspace commit merge-failures to frontend Apr 29, 2025
… 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.
| 'MissingDiffSpecAssociation';

export type CreateCommitOutcome = {
newCommit: string;
Copy link
Contributor

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

Copy link
Collaborator Author

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.

@estib-vega
Copy link
Contributor

The rest looks good, so I'll just merge it and make the adaptions on my side

@estib-vega estib-vega merged commit 7d17423 into master Apr 29, 2025
20 checks passed
@estib-vega estib-vega deleted the merge-conflict-handling branch April 29, 2025 20:50
@estib-vega
Copy link
Contributor

Thanks again for the changes :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@gitbutler/desktop rust Pull requests that update Rust code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants