I had a situation lately where I had a very very large file in my repo directory that was untracked (but not gitignored). This caused the

git update-index

etc steps to take more than 7m 😅 and very much confused me as to why

gt sync

was "hanging" (not `gt`'s fault in the end at all). It would be nice if such huge files could be detected and warned about in

--debug

logs at least (even more ideally to

stderr

or something generally) so as to explain what's going on 🙂

Reviewing large PRs in graphite is quite a chore. I understand some of the constraints that make it a hard problem to solve, and I've generally landed on an OK workflow. One minor annoyance that I hope can be fixed is this: I hover my mouse over the 'mark as viewed' checkbox. I approve the file. My screen scrolls (great!). I go to expand the next file by clicking its title bar (moving my mouse slightly left). Instead, I click on the 'Mark as Viewed' informational popover and my click is ignored. I have to move my mouse again to aim around the popup. If we could make the informational popover above the checkbox instead of to the left, you'd save me hundreds of dead clicks a week.

Hi folks! Just writing in with a feature request: It would be lovely to be able to have named stacks that you can collapse. With AI I now have a number of pretty big stacks, which creates a lot of noise in my inbox. I would like to be able to show PRs grouped by stack, and I'd like to be able to collapse/expand those so I can sort of ignore stacks that are currently backburnered or are in lengthy review processes while I focus on more current stuff.

Today I found the team plan is limited to 30 synced repos, when the website and pricing documentation doesn't mention any limits... 😕 You should at least update the pricing page to make this clear.

Hey all, hopefully a small/quick feature request. We work in a code base with heavy code generation (protobuf generating Go and Typescript implementations with some additional generation around database types), and sometimes a small change which by hand has actually only modified say 6 or 7 files ends up with a 70 file change (most of the other files being generated generated). We mark all the generated files as generated using gitattributes with

linguist-generated

tags. However it still causes PR's to be really hard to read what's actually changed (and the Tour mode gives up when too many files have been changed). Would be it be possible to have a setting which automatically groups generated files into their own section at the end of the PR, meaning only manually changed files appear at the top? (i.e. so as you scroll through the PR from the top you only see human changed code, before hitting all the generated code)

Support conventional commits in

gt submit -ai

: I would be great to still use ai for PR title and desc, but ensure ai uses conventional commits to build the title. The ai can make really nice and quick decisions on the scope, and even wether the commit is feature, fix, ...

i'd like it if i could see/edit comments while using the WYSIWYG markdown editor while editing as comments often contain template guidance

i'd like to use negative search filter in the files list of a PR. eg

!*.test.tsx

Is there a way to adjust the PR inbox to group and order PRs by stack? It would make it super easy to view and navigate the inbox

just thinking out loud... today is the first time i've seen a section collapsed in a 'code tour' not sure how i feel about it; feels like it encourages me to skip over looking at the tests, but tests are pretty important.

wouldn't mind having

⌘

k

then "`unfocus comment/file/etc`" so i don't have to manually purge

#thread:ajdcwiodajmwoiadjwd

from the end of the URL.

It would be really great if the PR view in Graphite could render Mermaid diagrams. They show up in Github's PR view, but do not render in Graphite.

I'd love to have an option to place the PR description and PR-level comments (not inline) in a side panel, whether that's with the incline comment panel on the right, or a separate panel. I often find myself with two windows open - one to see the description, and one to see the diffs

The vscode extension has potential, though some aspects could use improvements • when I click a file in the graphite diff view it does not include a breadcrumb, and does not highlight the file • it didn't recognize that I have graphite installed w/ brew already, despite having an option to install w/ brew, so I had to set the path explicitly then refresh • I can switch branches, it looks like I can move them, but I'm not seeing anything to fold/split, and the tooltip for the drag handle doesn't mention whether reorder is supported • I don't see a way to add inline PR comments or view them • I don't see a way to view the PR description checks, or top-level comments

Oh re https://graphite-community.slack.com/archives/C02DRNRA9RA/p1781879729156779 I would love a shortcut to copy just the current PR in ☝️ this format. I copy/paste the stack and pull out a single PR multiple times per day.

when i'm in

tour

, i often try to hit

f

to see the files (to quickly jump around) but it just toggles the table of contents for the review headings. (will submit via

gf

as well, just x-posting here for discussion/viz)

For the comments in Github that show the stack, it would be really helpful if Graphite merge statuses could be shown alongside the Github ones. It’s always so confusing for people in Github when everything appears closed, but some PRs in the stack are actually merged.

It would be really useful for my team's usecase for the default view of a PR to be the "Changes since your last review", like what I have selected in this screenshot. We have our workflow set for GitHub to automatically dismiss stale reviews using the oss action as documented in graphite's docs, but if I then get linked later on to the PR it's useful for me to be able to narrow-focus "This is what CHANGED since you last stamped it". Thatway if I did a review on a 2k line PR, then they changed one line, the next time I am asked to review it I only see the one line and can instantly approve. Then have a banner at the top of the PR view "You are viewing changes since your last approval. [Click here to view the entire PR]" so that users know they're looking at a subset of the PR.

It would be nice if files get virtualized. For really large PRs (>100 files changed), I need to click on files individually to load them. It’s a hugeee pain in the ass. I just end up going to github to review these types of PRs because github virtualizes it on scroll

Can you support nushell syntax on the diff viewer?

⌘ k / keyboard shortcut to copy ALL threads as markdown, not just one at a time

gt doctor

to debug when you end up in a weird state.

/grill me

(matt pocock) but for every PR. would be soooo useful for understanding/confidence in changes as both author and reviewer. workaround: 'agent' sidebar (cursor) w/ skill.

check 'added to review' (pending review comments) by default

is there a way to use

gt

without graphite backend i.e. i don't want anything to be uploaded to graphite servers (working on highly sensitive stuff)

I'd like to be able to dismiss this banner

github.blog/changelog/2026-07-30-stacked-pull-requests-are-now-in-public-preview Stacked requests in github are public. I would be awesome for graphite to support them!

It seems Insights only tallies data ( lines of code added for example ) when it's part of a PR. We have some devs who, depending on project and their team culture, commit directly to main branch. I'd love to be able to see some stats related to their direct commits to a main branch. • Direct commits w/o review • Lines of code added w/o review • Lines of code deleted w/o review • Total lines of code added • Total lines of code deleted

Also related to Insights, it would be great to be able to • Easily see comparisons to previous time periods and view trends • Export reports

hi guys i used graphite's merge feature for the first time (previously only merged on github) and to my surprise graphite merged PRs with their description, even though in github it's explicitly configured not to take descriptions when merging. Is there a setting in graphite for this, or can graphite respect github's setting?