Hi, I'm trying to sign up for the Graphite Core free trial, but when I click "Start free trial", I'm redirected back to the home page and nothing else seems to happen.

Hi Graphite team! We've been having some issues with the Graphite Slack integration notifications - attached a video below (clicking the graphite notifications does not clear the notification count compared to other notifications). Let us know if this is something you can repro/fix on your end (could a Slack issue as well) - really appreciate it!!

I don't think this is a bug, but the way Graphite is not that compatible with a Monorepo(Turbo repo). Team of 8 engineers. 5 packages in our mono repo. Merge to master happens 3 or 4 times a day. GHA cache is immutable, scoped and doesn't share artifacts between branches. That means that every time you ask Graphite to merge a big PR stack, it will duplicate your PR stack creating it's own PRs, with 0 cached layers and it will take 25-30 minutes for each of our PRs there. This also means that it will flood the cache (that's limited to 10GB) with 1.6GB worth of entries and will evict important and older entries (like from

master

) and will make the CI fail due to this. This became an issue after we moved to a Mono repo and we saw our cache entries grow larger and larger. Any plans to change the way this works, or suggested work arounds?

I realized my Macbook was unexpectedly full. I looked to understand why I discovered that

~/.local/share/graphite/debug

takes ~463 GB. 🤔

We just have an interesting case with multiple trunk configurations. Just to quickly explain the setup: • Engineer A creates a stack of 2 PRs (amount doesn't matter) on

main

(our default trunk) • Engineer B does a

gt move

onto another trunk (configured locally), lets call it

release-B

. And does a

gt submit --stack

and the review shows nicely that the 2 PRs are now depending on

release-B

and not

main

anymore, • Engineer A does a

gt sync

but nothing changes • Engineer A instead also defines

release-B

as additional trunk and then does a

gt sync

on their 2 PRs and only not they are showing up in the correct location. To us that is a bug because Engineer A only didn't push and overwrite the changes from Engineer B because they are sitting next to each other. But otherwise they would have not be notified. I would enjoy to get a message that says, your stack has been moved to an alternative trunk, do you want to sync this move locally, similarly to when it happens that somebody adds a PR into your stack you also get such a message (which is amazing btw).

feature request: add horizontal scrollbar for markdown tables in github comments. github itself does that, but graphite squeezes the table to fit, leading to weird results sometimes

is graphite down at the moment?

is graphite down?

We’re having an incident - investigating

Yeah my team is having trouble accessing Graphite and I just saw a pile of 503s

Latency should be recovering now

​*[Monitoring]*​ Graphite - Database performance issues causing site slowdowns We implemented a fix and are currently monitoring the result. ​*Affected:*​ Dashboard, Slack notifications, Merge queue, CLI View incident button

​*[Resolved]*​ Graphite - Performance issues causing site slowdowns This incident has been resolved. ​*Affected:*​ Dashboard, Slack notifications, Merge queue, CLI View incident button

I had a PR that was all ready to go (green and up-to-date with

main

). I had added our merge queue label before the build finished and thought the queue would merge it quickly. Instead Graphite pushed a new commit which triggered a new build, delaying the final merge. Not a big deal in this instance but I’d like to understand why because that’s wasteful

Tried everything, this still won’t work anymore

I'm trying to add a merge queue, but I'm being told the repo has branch protections that are preventing it But the repo in question has no branch protection rules, and any rulesets have Graphite App on the bypass list with 'Always Allow' - am I missing something or is this a bug?

Hi all, I just joined a new organization who was already using graphite. They have made me a graphite administrator which is great. However something is broken, I cannot be added as a reviewer to PRs. I'm both a admin on graphite and github so I'm at a loss as to why this would be the case. I think it must be something misconfigured in graphite itself since I can be added as a reviewer in github

Is it a bug that the “syntax highlighting language” selection is reset upon refresh of the page? (I keep setting it to Elixir for the .livemd filetype whenever I need to review a Livebook file). Or is there a setting somewhere I can make the selection permanent?

Hi team! I recently noticed that we can't upload

.mov

to PRs now in graphite? Was this an intentional change?

I noticed that

gt modify

is now committing all files instead of only staged ones. Is this a behavior change or a bug? sad parrot

Ever since the merge queue improvements, I’ve found that

Merge when ready

isn’t working. Anyone else?

Topic: Potential PR Merge Bug Please review this Loom. Please note that the reviewer can merge the branch in GitHub.

I'm working with a friend on a community Github repo and when I click "Join Team" on their repo, I just get an error. Is there a way for them to add me? This is collaborator on a public personal repo, if that makes a difference.

compare versions doesn't seem to work for me

Graphite extension doesn't seem to be available anymore in vscode marketplace

It claims this PR doesn’t have the required approvals when it does

hi, we're seeing an issue where when a CI job fails, the AI-generated summary is "stuck". it very often says this same thing -- even when the logs in the failing CI job are totally unrelated to rabbitmq.

Hi, I've been seeing an outage for about 30 minutes now.

gt submit

fails with

2025-07-10T12:22:15.927Z: Error: Error response trying to pre-submit PRs: 500

Hi Folks, I have the CI Optimization set up but everything the bottom stack is merged the skip trigger returns false and the CI in all stacks above runs. I am sure that everything was synced and good to go. That is the third time that it happens. It even dismiss the approvals. How can I investigate it better or provide any data for debug?

Hello! I had a stack with main -> A -> B -> C, all got approved and decided to merge the stack. However, A got merged, B needed a re-approval (not sure why), C got merged into a

graphite-base/

branch and got closed. I had to reopen C, create a new PR, get approvals, and then merge it into

main

. Am I doing something wrong or was there an issue here? Trying to understanding what happened here.