This message was deleted.

Currently what get's done is: • if you haven't deleted locally you can repush to a new remote • you can manually recreate the PR 😞 • ???

I actually did this to myself the other day 😬 unfortunately there is so only so much we can do to discourage accidental merges on GitHub that will break things. We can definitely do a better job of handling this case! I'll look into it. The somewhat more immediate issue to me is that a Graphite merge somehow merged into the wrong branch! We have a lot of protection in place in our merge system to try to prevent this, if you DM me the PR number we can look into this bug

I think the issue was something like: merge the full stack of prs, while "merge when ready" was active on a branch from off the stack in the middle

Thanks for the video! Ideally I'd like to detect this on repo sync and prompt to fix 🙂

just refetch branch and re-track and resubmit

Seems obvious in retrospect. I screwed up on this the other day and just merged the messed up stack. This seems like something that the Graphite Chrome Extension could help with. It wouldn’t stop cases of people merging in PRs from mobile (which I often do), but it could catch the issue for people on web.

we do currently add a link above the merge button that links to graphite with the merge modal open!