I had a badly formed regex pattern in my PR, which was caught by a Github code scanning alert. It's been updated and closed in Github since, but I'm unable to resolve the thread in Graphite. (not clickable) Dismissing the alert also didn't resolve the thread in Graphite.

(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using

gt feedback --with-debug-context <any message>

Hi Queen, Apologies for any inconveniences this is causing. Can you try seeing if you're able to resolve this in the new PR page we just released? Go to Settings -> Preferences -> New PR page

Ah! ...or not ^^; This allows me to press the "Resolve" button, which initially shows "Reopen" then immediate flips back to "Resolve" with an

Unexpected error

modal. I've left feedback and linked this Slack thread

Ah no okay, is it possible to delete this comment in Github so this PR is unblocking? I am working on a local repro now, will likely flag this as a bug

I'm not sure how I'd be able to delete the comment actually I don't think it's the first time our team has enabled this agent (maybe it was before using graphite?), but I'll ask my team. And yes, this error occurs on every comment from this agent

Got it, I have flagged this bug to our team for prioritization. Thanks again for your feedback As a workaround, I would encourage merging this PR through Github and then running

gt sync && gt submit

for the remainder of the stack after the merge finishes to continue on Graphite

ahh sounds good, thank you for the quick responses on this, I appreciate it!