# Fix bad GitHub merge queue merge \(\#54721\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/9b40411c6ab5957d43ffefd070ceafdecf1a0f2b)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 9b40411c6ab5957d43ffefd070ceafdecf1a0f2b

Requested commit: 9b40411c6ab5957d43ffefd070ceafdecf1a0f2b

Commit: 9b40411c6ab5957d43ffefd070ceafdecf1a0f2b

Tree: f3e7be24c4fe382d9b3b42893bcbb1dbfe92feb7

Author: Finn Evers

Committer: GitHub

## Message

```
Fix bad GitHub merge queue merge (#54721)

No, sadly, the title is not a typo. See
https://www.githubstatus.com/incidents/zsg1lk7w13cf for the context.
I'll read with joy and popcorn through that root cause analysis.

It makes literally zero sense what happened here, but for some completly
bonkers reason GitHub completely messed up the merge queue with
https://github.com/zed-industries/zed/pull/54632.

I have no idea how it happened. It makes literally zero sense. A PR
going into the merge queue should have the same LoC when getting out of
it. GitHub obviously does not check this. GitHub causes extra work with
a feature that is supposed to save time.

Thanks, I guess.

Release Notes:

- N/A

---------

Co-authored-by: Danilo Leal <daniloleal09@gmail.com>
```

## Parents

- [a1cb3706f4f02ca07ad480c511be8c27edc50b18](https://git.cafe/gitcafe/zed/commit/a1cb3706f4f02ca07ad480c511be8c27edc50b18?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/9b40411c6ab5957d43ffefd070ceafdecf1a0f2b?format=markdown)