I've started getting

Your org has enabled the Graphite merge queue for merging into main

comments on my PRs even though I'm authenticated and Graphite works fine, is there a way to fix this?

Same, I’m an org of one and still got this message even tho I’m the one who enabled it.

hi both! we recently added this comment for clarity - it appears in all repos with the MQ enabled. unfortunately we don't have settings to configure this just yet, but please let me know if it becomes too noisy and I can let the team know!

it seems really strange that you would both comment

Current dependencies on/for this PR:

and the huge merge queue comment in two separate comments

I would definitely like to disable it. Since I’m an org of one it will never serve the purpose it’s meant for, and provides no value to me, so it’s pure noise.

thank you both for understanding!! the reason why it's not currently part of the "current dependencies" message is because the MQ comment is meant to remind folks to merge via MQ (when it's enabled), even if the PR wasn't created on graphite (in which case there wouldn't be a "current dependencies" comment to add to). we're still making updates to this, so hopefully will be able to make it less noisy for users who find it less helpful!

@Joyce Lu Another pain point with this comment is that, since it's posted by the bot and not by the user like the regular Graphite comment, it shows up in GitHub notifications, so whenever I open a PR now I immediately get a ping from the GitHub bot that I opened a PR

got it - thanks for raising this as well. i'll check with the team to see if there's any way to work around this

thanks!

Just wanted to bump this thread because this comment has gotten annoying enough that I’m starting to consider disabling the merge queue entirely or hacking up some way to auto delete. Took a look through settings and couldn’t find any way to disable so I figured id check in to see if there were any other workarounds or plans to make this comment configurable before I do anything drastic?

Same, had another teammate bring it up on Friday and I said I'd probably just disable the merge queue altogether given that this doesn't seem to be getting resolved any time soon

hey folks - thanks for bumping! let me get the latest for you