Hi 👋 curious about some discrepancies in Insights I'm observing. I see users who had previously been Graphite users who were decommissioned from the repo being excluded from historical data in the Insights user list. Based on my interpretation of the methodology here I wouldn't expect this. • Is this intentional? • Are their contributions still aggregated in overall stats or are they excluded there too? Thanks for any direction/ideas here!

How should I setup my GitHub actions CI requirements if I use CI optimization? I found that if I just skip required tests that are optimized away, then Graphite can merge multiple PRs at once, even those that didn't get all checks run. I'm now adding a final check which fails if CI optimization was triggered. Is this the correct approach?

hey all. we're having issues with github actions and graphite. we have sql migration that runs on prs on main that are closed. but only the bottom diff in a stack is triggering this. wondering if we should try triggering on push to main instead and if there are any other settings we should try?

Hey team 🙂 How to create filters for the PRs in graphite UI and share it with the whole org ? For now we only see a URL sharing 😄 Thank you!

hello -- i was on vacation and when i came back today, my graphite was no longer authorized to my team's graphite. when i tried to re-authorize, i'm getting "missing permissions" for the repositories under my org. i have been granted permissions to my org's repositories so i can't tell what the issue is. would appreciate some support here 🙏

hey all - we were wondering why Graphite needs these temporary draft PRs when using the parallel CI feature in the merge queue. Unfortunately the docs only explain the how but not the why. We were wondering if it would also work with just temporary branches to avoid the PR spam?

Hello! Because not everyone is using Graphite around here, we’re testing out the GitHub merge queue instead of the Graphite one. There’s one behavior that felt surprising to me with a stack: I marked the stack as “merge when ready”, updated the stack, and waited. The first branch was added to the queue, then merged. All good. The second PR started to point to

main

and was added to the queue immediately. However, I was expecting Graphite to rebase it but it didn’t. So the commits from the first branch were there, along with the associated diffs, even though they didn’t make sense since

main

already had these changes (probably a GitHub problem). The issue for me is that it makes the PRs of a stack confusing and misleading. If someone goes back to that PR later, it won’t be clear what it actually changed. I know you recommend using your queue, but is there a solution to this? Is it the expected behavior when using the GitHub queue? I’d prefer taking the hit of another round of CI on that branch, if Graphite could automatically rebase instead of adding to the queue as-is.

For Vimium users (and similar tools): this means you’ll have to create an exception for the new domain. I was confused for a moment why

g i

didn’t do the right thing 🙂

Where do I go to get billing help? I was trying to sign up for a monthly plan that had PR reviews, but my billing portal is in a weird state: • It says I have a plan that ends Sept 8, 2026, and that my next bill is $1.2k • My invoice history says that on Sept 8, 2025, I was charged $0.0 for Graphite core Given that the billing state seems so weird, I’d just like to cancel my service and not pay for a year’s subscription

hey team! is there a way to configure a branch naming template when the cli auto creates a new branch when running

gt create

Hey team 😄 Is there a way to know at all time what is in the merge queue ? I'm building docker cache in our CI and one edge case with the merge queue (with ci optimizations enabled) is to import the right docker cache. In the case of a stack with a single PR, I can just import the cache of the master commit base. However, if there are two stacks in parallel, for stack 2, I'd need to know the PR numbers of stack 1 😄 Thank you for the help 🙂

Is there a best practice for merging trunks? For example, I have an

integration

trunk that I want merged into my

main

trunk for a new release. Or using the example, merging

release-v10

into

main

I have a PR on top of a PRs stack. All are merged but the top one. How can I move it to main to remove it from the tip of the PRs stack. Moving to main (gt move...) does not work, as gt already considers it on main. Is there a clean way to do this?

QQ Is there a way to take a full stack of PRs and squash them down into a single commit onto main instead of merging each individually generating one commit per PR?

Q about merge queues - regardless of merge strategy will graphite always create the separate PR and then close the PR I created instead of merging?

Is there any way to skip the merge queue? I specifically want to do that when it's just a single PR that I want to merge. It's not part of any stack. It's just one PR on its own. And I want to do a squash and commit merge on it like I would do on GitHub without going through graphite's merge queue. Currently, I always have to switch to the GitHub PR tab for it, but I wonder if I can just stay in Graphite and do it from there.

hey team, I recently saw a Theo vid and trying to checkout Graphite however, I seem to have come across an error on the test PR

PS C:\Users\mynameistito> gt demo pull-request
√ This directory (C:\Users\mynameistito) is not a repository.

We recommend that you run the demo in a remote repository so that
you can submit your pull requests to GitHub and view them in the dashboard.

If you don't have one handy, we can create a temporary repository for this demo.
Would you like to continue with a temporary repository? ... yes

Created temporary repository at C:\Users\mynameistito\AppData\Local\Temp/095b8d8c/graphite-demo-repository


# Intro (Step 1 of 4)


The goal of this tutorial is for you to learn which gt commands map
to your existing workflow, and get you comfortable with creating a
single pull request on Graphite.


You'll only focus on a single pull request for now, so you can get
comfortable with the core commands. After you complete this demo,
you'll run gt demo stack to level up to creating stacks of pull requests!


This demo will often stop and ask you to try running commands,
via a built-in shell we provide.

EXAMPLE: Run ls to print the contents of the current working directory:

graphite-demo-repository main
❯ ls

ERROR: Could not find a path to 'ls' binary when running command: 'ls'

graphite-demo-repository main

If anyone could help me or point in the right direction that would be great (I did have issues with some path env stuff to by the seems to so not to sure if its related.

Can Diamond inspect the description as well as the code? For SOC purposes, we need to ensure that the PR descriptions are filled out, and sometimes people forget (or forget to link a JIRA ticket when there should be one, etc.)

im a solo dev that only uses a personal GIt repo. but automations etc. which are what i was about to sign up for. can't work on personal repos.?

Is it possible to disable Slack notifications from dependabot specifically? It isn’t recognised as a bot user and it is also not recognised as a user I can then mute

Getting

Couldn't sync <branch> as the current remote version was not pushed with Graphite.

Last night I was able to

gt submit

this branch and this morning I'm not. On app.graphite.com the stack looks fine; I'm even looking on GitHub and can see that every single push says "force push" which for me means I did

gt submit

rather than

git push

; All commits on this branch were made with

gt modify

. What the heck do I do? I am totally stuck, I have no idea how to proceed

Does anyone know how I can sync graphite web UI with my local stack? Sometimes I will reorganize and split some stack branches and end up in this state where I have `gt delete`'d branches locally but graphite doesn't update the web UI so I have to put notes like

IGNORE

on branches that are no longer to be considered. This is 2nd time its happened to me so reaching out for help.

Is there a one-character alias for

--restack

in

gt submit

? It appears not. Can you please make

-k

an alias for

--restack

? When I

gt submit

, it totally messes up my flow when I realize nothing has happened and my terminal says "are you sure you want to restack?" I've often switched branches and am doing something else! So I always use

gt submit -s --restack

but it's pretty verbose. Any shortcuts for that besides a bash alias?

We're migrating to using ZScaler which is currently configured to introspect TLS traffic to graphite domains. The graphite CLI fails with an underlying error of

unable to get local issuer certificate

in the

--debug

output. Basically it appears that we need something like this to be called within the graphite CLI, but I'm not able to see this option anywhere. Is this possible to setup?

const tls = require('node:tls');
tls.setDefaultCACertificates(tls.getCACertificates('system'));

say i have two repos (frontend, backend), i made changes to both, how do i stack PRs across these two repos?

how do I force an Action? "Optimized to run later" I would like to run some manually

Hi, is there a way to turn off previews of app.graphite.dev URLs in Slack messages?

Maybe it's me just being impatient, but I feel like the ui gets stuck a while on

rebasing

after a merge in a pr, even after I rebase manually from the cli and I can't do gt merge right after. What does it actually do when it rebases from the platform? how is it different from the manual rebase from the cli?

How do I get back to the "previous" version of the PR page? I'm finding so many usability issues in the new one and really want the old one back. I've been filing feedback and I know y'all are working to improve it, but I really don't like that I cannot get back to the previous version of the PR page. Feeling frustrated and stranded on this new one 🙃

hello! Every time

gt

connects to GitHub I see these lines about Yubikey:

🚀 Pushing branches to remote...
Please tap your YubiKey each time it flashes to continue

However, it never actually asks me to tap it, it goes through without an issue. Should I be changing something to not see that message? Not a big deal of course, I’m mostly curious.