Hi! Using Linear in conjunction with merge queues are not working so hot for us, since the original PR gets closed rather than merged he issues in linear stay open. Any advice? :)

(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state

A PR is tagged with a Linear issue, the issues properly tracked and the status is updated with in-progress and in review as the PR changes state, but when using ”add to merge queue” the PR is not actually merged, but rather closed, which is tripping linear up. I understand that the PR is closed for technical reasons, but do you have any pointers on how I can retain the same workflow regardless? :)

We're having the same issue. I will give this a try

Wow, thanks for sharing! 🙂

Yea no problem. Curious what will happen on stacked PRs reffing the same Linear Issue

hey all, yeah Linear can also detect the

externally-merged

label if it is added before the PR is closed. This tells Linear to treat the pull request as successfully merged even though it was closed. See Linear’s documentation for custom merge queues.

@Johan Brodin do you use the Graphite MQ? I don’t remember having that issue with it, and we don’t have it with the GitHub merge queue either right now. 🤔 I always put

Fixes LIN-1234

in my commit message, which always ends up in the final commit message on

main

, so maybe that’s part of it? I typically use the Linear branch name as well