One of the pain points for my team is that we use ...
# how-do-i
t
One of the pain points for my team is that we use JIRA and GH integration. Using Graphite MQ, the original PRs always get shown as closed. It's confusing for non-technical members and it actually kills any ability to do JIRA automations when a PR is "merged" (because Graphite MQ closes the original PR) Is there anyone with a similar situation w/any suggestions? It's problematic enough our team might have to revert back to GH merge queue 😞
p
(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
hey Tim, unfortunately this is due to a restriction on GitHub's side that doesn't let us override those PRs as merged. There's more info about this in our documentation here. If you use tools that monitor whether the PR is merged, your integration may stop working. Many tools have options to monitor merged commits rather than PR status: for example, see Linear’s guide on linking commits*.*
s
I do wish there was at least a label you could ask to add so it was more obvious which PRs got merged. My company did work with the merge queue folks to try out "purple merge" and it's been working wonderfully for us to get merged PRs
t
Hey @Gareth Brickman related to this, are there any Graphite automations or workflows Graphite can recommend to translate / ensure branch tagging gets added to the commits within the MQ PR? Relying on all users to add the "Fixes ABC-123" isn't resilient enough for us to try using Merge Queues without risking our ticket hygiene?
p
hey Tyler, there isn't a Graphite-native way yet to perform PR labeling or branch tagging for that use case