Our temporary merge queue branches seem to not get deleted anymore. This started on the 15th. The branches merge but don't get cleaned up. I don't think we changed any Github or Graphite settings when this started.

I added an empty account to use the insights for BI purposes. But I’m getting 404 on api routes that show the User list.

For the past week or so, files in pull requests have been heavily truncated inside of Graphite. Here's an example. Note that the top file, for example, added 86 lines, but it's only displaying the first one. This happens sporadically (but not infrequently) and it persists through a refresh.

Hey Graphite gang! Us over at Tennr just started using the merge queue today. We're finding though that now our Linear tickets aren't automatically moving to Done when PRs are merged. The PRs are showing up as Closed in GitHub, and the tickets just stay In Review. Is there something we can enable to keep the behavior where they move to Done?

I've recently started seeing a few "positive reinforcement" comments from the AI reviewer that basically boil down to "this code does a good thing". While the good vibes are appreciated, such un-actionable comments are a bit distracting. Is this intentional? — I don't see anything in our custom rules that would push the AI to leave such comments.

Hi, I'm experiencing a bug, my team has an automation to automatically add reviewers to PRs. Usually this works and adds everyone, but sometimes it will leave someone off (adding say, 5/6 team members). I've experienced this periodically going back months, but it seems to have been happening more and more, with myself not being added to PRs as a reviewer multiple times over the last couple of weeks.

This bug came back. I’m alternating pressing

f

and

1

.

“Needs your review” section is in a permanent loading state

yet again seeing merge conflicts introduced in PR stack by graphite:

Struggling to enable Diamond on our repo

suvera-monorepo

in the org

suverahealth

I click enable on https://app.graphite.dev/diamond?org=suverahealth pick the repo, add settings and click save. It appears for a second to have worked and then goes back to the default landing page asking me to enable it

We are currently struggling with a merge queue which is not merged, although all checks passed etc. for over 2 hours now. When I open the lowed PR in GitHub it is stuck in this loop here, does anyone experience anything similar? status.github.com says everything is fine on githubs end

This message was deleted.

Minor ui bug when a label is too long

I was double-notified of this comment

👋 Mini bug: you cannot see the user name that reacted to a comment in a PR, when the user is a bot

Can't enable Diamond, after clicking Enable and choosing our repository, it flickers to "Enabled on 1 repository" for ~1 second before going back to the starting screen with an "Enable" button

This message was deleted.

bug report: this keyboard shortcut doesn't work for me (though the other shortcuts that I use & love & cherish in your webapp work great!) I do the shortcut and it seems to be toggling-mark-as-complete for one file, rather than marking-as-complete the file that I'm currently scrolled-to in the list (maybe there needs to be an IntersectionObserver or something to notice "which file is currently visible on the screen"? dunno!) steps to repro: 1. scroll through a long PR with lots of files in it (dunno if this is strictly required) 2. press

command-return

to trigger this shortcut expected results: it should toggle the "Viewed" checkbox for the file that i'm looking at actual results: it seems to toggle the "Viewed" checkbox for the same file over and over, even if I've scrolled way down on the screen

I keep getting

ERROR: Your team's Graphite plan has expired. To continue using Graphite in oh-my-goose, upgrade your plan at <https://app.graphite.dev/settings>

from

gt sync

tonight. But I check my plan (free plan) and it looks fine. Does anyone know what happens?

Sometimes the CLI changes the base branch to

graphite-base/[n]

. When does this happen? It sometimes breaks

gt get

afterwards, because the CLI will error that the PR has not been created with Graphite. People are on the latest CLI version.

Hi, I really like using the VSCode extension. However, there is one area that is painful to use: the commit message input. Here's a list of what's not right: • if you leave the extension tab, the message is lost • if a pre-commit hook fails, the message is lost • if I type too fast, some characters are lost 😭 (hard to record though as it mainly happens when my CPU is busy) • it would be great if pressing the UP arrow would show the last entered message (like the default behavior for VSCode commit message input)

I am having the “`graphite-base` branch doesn’t exist” issues in GH CI, as previously discussed in https://graphite-community.slack.com/archives/C02DRNRA9RA/p1741801162679489?thread_ts=1737026419.655359&cid=C02DRNRA9RA. What is the current state of this? It sounded in that thread like there was a feature flag I could ask to be flipped in my org to make the problem go away? Is that still the case? What are the downsides of it? Ty!

https://app.graphite.dev/github/pr/CondorSoftware/condor/5718/Fix-forecast-ending-earlier-than-expected-for-an-edge-case is stuck “Waiting to merge…” indefinitely

Hello, I keep trying to enable Diamond on a repo, I click save, it refreshes to this... It's also not clear if I can just try it on an initial set of PRs to see if it tends to spam

It says Diamond left 1 comment when she actually left three

Hi team, as of a recent Graphite update a few weeks ago as soon as I enable the Graphite VS Code (/Cursor) extension there is an avalanche of Git processes getting spawned constantly - I’ve tried both the homebrew and NPM variants of the CLI with the same result for each although I could swear with the homebrew one it was worse the fans on my M4 Max mbp would constantly spin up

gt --version
(node:96999) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
1.6.1

Extension version 0.6.1

Hi team, just found that this description area recently got width auto expanded to full width in edit mode only. This is really annoying because it is ONLY full width in edit mode, causing a UI flickering.

Code blocks with

plain

should not do any code highlighting but do. https://app.graphite.dev/github/pr/spockframework/spock/2157/Make-the-preprocessing-tasks-for-workflow-files-cacheable#discussion-IC[…]OABG6hs6pZ9k1 is displayed in GT as

Graphite should not be notifying me about comments mentioning me from

@graphite-app

I can’t leave any comments on this PR. Refresh does not help.