I feel like cmd-k should be able to be a lot faster if i type in the exact pr number

it would be awesome if comments in Graphite's PR view showed which version was active when the comment was made

We sometimes have a stack of PRs to simplify the review process, but we do not want to merge the PRs individually - only the full stack at once. I'd like the ability to fold a stack before merging, and the ability to create stacks with a fold-and-merge when ready flag.

I have some devs who only use the ai-generated PR description, which is negative value for me - I care more about why they're making the change, and what alternatives they considers. I'd like to disable ai summaries for my tenant completely as a feature flag.

I’d love it I could easily create a Linear ticket from a PR thread. Let’s say we had some discussion on a PR where something could be improved by caching. I may not want it to be a blocker for merging that PR, but I would want a Linear ticket to add that caching so we don’t forget and lose track of it. Right now, I’ll leave a comment asking the PR author to create that linear ticket before resolving the discussion thread. Would be great if Diamond could just do it for me.

Hi We used to use the github integration in linear to automatically close tickets when their respective PR is closed. When we added CI Settings to not run CI on every PR in the stack, it has this note:

Note: A temporary PR will be created for every CI run which will include all the commits from PRs in that stack. After merging, this temporary PR will be marked as 'closed' on both Graphite and GitHub. Learn more

Unfortunately this breaks the github integration in linear - since the PR with the ticket is "closed" rather than "merged", and the temporary PR is what is merged instead. Is there a workaround for this? Or - idea - can we add this type of integration into the graphite integration to linear? Would be great if this integration had the same ability of the github one to manage ticket status

I’d like to separately enable/disable notifications for “Someone approves your PR” and “Someone requests changes on your PR”. The latter requires action from me, while the former doesn’t.

An option to stage all already-selected hunks and stop going through additional hunks. It’s a pain when I have many files changed and already got all the ones I want.

When I click on a thread in "activity", highlight it when we scroll to it so I know where I was in my list as I go through it.

hi there! bumping an older request (past history limit in Slack, i think) • better

Fold

support ◦ eg don't show

closed

if it got folded/merged • (and/or) generally better 'merge' support in the Graphite web UI ◦ eg being able to merge any branch into its target, not just the one branch targeting

trunk

both of these frustrate + confuse my team frequently.

Hi Graphite Team, I really enjoy the product and wanted to know if there were plans to make a mobile app version similar to what github has? Thanks!

It would be great to configure the "Review request response time" and "Time to first review" Insights metrics to respect business hours. For example, if a developer submits a PR for review on a weekend, the clock shouldn't start ticking until the next business day (e.g., Monday at 9 AM). This would provide more accurate metrics by excluding non-working hours from review time calculations, giving teams a clearer picture of their actual review performance during active work periods.

With merge queues, it ends up re-running CI for even a single PR merge that is already up to date against the trunk. Aside from being redundant and wasteful in terms of costs, it also just needlessly makes single PR merges take longer than they should. For this reason, we often merge such PRs directly on Github. But this gets to be a problematic habit because people get so used to doing it sometimes that they’ll merge stacked PRs down into a parent from the Github UI. Would really appreciate if the merge queue could skip the work if it’s unnecessary in this case.

multi repo stack for cross environment dependency management example usecase, i put up one pr for batch job in my backend repo then create a dag to run it in my airflow repo the airflow pr is dependent on the batch job existing, and such it would be nice to stack these changes. maybe internally you could just maintain two stacks on each repo trunk and link to each other other usecase would be in my migrations, i am rewriting backend from scala to python and use internal api to talk. so would be nice to again have a stack for a change across both environments, so i can manage dependencies explicitly in the stack. or even more than 2 repos, some pr for batch job that creates db artifacts -> data processing layer pr, like some etl pipeline for auditability, -> airflow prs to schedule

Would it be possible to get a

GT_CONFIG_DIR

variable instead of relying on

XDG_CONFIG_HOME

? It would provide user much more control and flexibility in how they configure and authenticate graphite.

Feature Request Currently we have some gen/ files that we use throughout our codebase that we don't include in the

.gitignore

. We were wondering if it would be possible to create a

.graphiteignore

file that could ignore those files in the

git diff

view on Graphite.

Hi guys my company of 50 engineers is all in on Graphite its a core part of our workflow. A feature we'd love to see is some sort if git bisect like functionality based on diffs. Lets say we have a large stack of PRs and want to run lint, typecheck and test on each branch locally. I would need to manually need to check out each branch and run it. It would be great if there was a configurable cli command in Graphite for this. It would be great if there was a linear bottom > up, top > down and bisect flag if possible. Thoughts?

hello! One thing I don’t like with GitHub is how there is no indication that someone started a review. So you could be in the middle of one and someone else approves the PR and boom it’s merged before you can submit your comments. It’d be nice if Graphite could fix that when reviewing from the Graphite dashboard. (possibly it could even be fixed when there are pending comments on GitHub…)

I sent out an internal survey about Graphite and one piece of feedback was this:

I still upload screen recordings through the GitHub UI because Graphite makes them open as a link rather than be directly embedded, and I don’t like that. So I put in placeholder text and switch to GitHub to upload the videos after creating the PR in Graphite. I wish Graphite could directly embed videos into the PR descriptions.

one thing I would love would be to simply be able to configure CLI to open the actual PR page rather than the stack page when creating new PRs. I never use those stack pages so I just have to wait until they load and click the "see PR" button

(btw I don't even get why that page exists at all)

yoo Graphite team, can we get a #feedback channel? i feel bad sharing into #C02DRNRA9RA/#C06C4TH0D27 🙈 sometimes i just wanna share some feedback and don't feel like i've got the right place to do that

would be nice to have an option to hide all comments from the PR review page (not just collapse, but hide altogether). This would probably be a checkbox on the page somewhere, like a "zen mode" When a PR has a lot of threads, it can become really difficult to read the actual diff 😅

The ability to re-generate an AI generated PR message and template. I have “Set PR metadata” in CLI enabled and sometimes when doing an AI submission it gets both the title and description wrong by focusing on the wrong thing. In that case I’d like to be able to prompt for re-generation as a next try. Something else that would help us is a tighter Linear integration, e.g. give the AI summary agent access to the linear ticket attached as additional context. I think that would already help a lot. Thank you!

Hello team. Is it possible to make the "Write your review" field non-required? I've already left my comments on the PR, I generally just end up writing "Comments in PR" in this field. Or am I missing something?

would be cool to have a merge protection feature in graphite that requires "an approval from any of the requested reviewers" github doesn't have this feature and it would be really nice! we don't have required approvals but it would be cool to automerge after an approval from someone you requested a review from

would be cool to have a stacked diff tree view in the web console with user avatars, pr status, time open, etc. (the tree view in vscode is awesome!)

Is the graphite vscode extension open source? I’d like to build a graphite extension for zed (only thing keeping me on vscode)

Also, Would be nice to collapse stacks in the vscode extension UI. I have some pretty large stacks (10 deep), and they take up a lot of space, even if I’m working in another stack

Nice to have: filter options that let me create a dashboard section for PRs with failing checks or merge conflicts