How do I allow

gt submit

to ignore if the

main

branch is behind

origin/main

? It's not usually relevant to me creating a PR. Steps to repro: 1. let

origin/main

get ahead of your local

main

by a commit or two. 2. click the "submit cloud" button in VSCode extension. 3. See

Aborting submit due to out of date trunk branch

is there a way to turn this on org-wide?

after i

gt fold

a midstack diff, vscode shows the diffs combined ✅, but when i click sync, the diff reappears on top of the parent diff ❌, but now at the top of it's own branch with no descendents ❌ expectation is that after the fold operation, diff is permanently combined how do i combine two diffs?

Do you guys have an OOTB cursor rules / claude MD to tell the AI how to use graphite CLI?

Hey is there a way to disable "escape" leaving a stack back to the dashboard on

<http://graphite.dev|graphite.dev>

? When navigating with the keyboard, it's often necessary to press escape - e.g. "E+R" opens the "edit reviewers" dialog, and then "escape" closes it - but if you accidentally press escape twice, you're out of the stack! I think "escape takes you away from a stack back to your dashboard" should not be the default, but even if it is I would really love a way to disable this.

Some CLI feedback: is it possible to do

gt sync

only for the current branch or only for the current stack? I often want to update my local branch to reflect the recent version of

main

but

gt sync

goes through all other open stacks and gives warnings about many of them. This is incredibly noisy and slow for something that, in my prior

git

workflow, I would do dozens of times per day and very quickly. I propose options like

gt sync --branch-only

and

gt sync --stack-only

that touch nothing locally except the branch you're on or the stack you're on.

Note: this reminds me of the famously unpopular default UX of `brew install`/`brew upgrade` which updates every package before installing or upgrading the requested one.

Say I have a stack of PRs:

main -> A ❌ -> B ❌ -> C ✅

Is there a way to kick Graphite to merge them all, since C fixes whatever was wrong with A and B?

How do we add more than one github organisation to graphite? We've linked a second one in synced repos - but has 1 of 3 repositories instead of 1 of unlimited. When I look at the billing page I just see a workspace name with the other org - and when we try to use graphite cli on the new org/repo we get an error saying that a plan is required. How do we enable the other org on the same plan? The committers are the same users.

Is there any ability for graphite to interop with Sapling repositories? It'd be great to be able to use the graphite cli to create stacks etc on top of a sapling repo. https://sapling-scm.com/

Is there a way to sync a PR with main from Graphite's UI in a way that will not remove approvals? We just started using https://github.com/withgraphite/dismiss-stale-approvals and it considers the "Update branch" button in github as a change which dismisses the approvals, but I don't see an alternative in Graphite UI for "update branch" - for context not all of our team members are comfortable with the CLI (e.g. QA)

Is there a way to list all my frozen branches directly, without having to parse output of more general purpose commands or sub-commands?

Hi! We're trying to set up CI optimizations with github actions. I have it configured to be topmost and 1 bottom most PRs of a stack to run CI. I am noticing that if i have a stack: 1 <- 2 <- 3 <- 4 with 1,2,3 being "ready for review", and 4 being a draft, CI doesn't run on 3. Ideally, I would expect the topmost non-draft PR of a stack to run. Is this expected or configurable?

Is it possible to submit to only the current branch, upwards? Instead of submitting to any downstack PRs as well?

Hello! I'm from January, a long time graphite customer. I realize we don't have a relationship with someone from graphite - is it possible to set up some time to chat?

Hi folks, my team makes use of stacked PRs for our development flow, but when it comes time to merge them they must be reapproved in Github one at a time. Looking at https://graphite.dev/docs/github-configuration-guidelines#required-settings, it looks like we'd need to disable

Require approval of the most recent reviewable push

which is a non-starter for us. We have

graphite app

exempted from our repository settings in github, but that doesn't seem to matter. Is there a way for us to get stack merges to work without completely turning off approvals on Github?

Is there a way to batch "resolve" with "reply" on a comment thread? It feels odd how the "resolved" state on a comment takes effect instantly but a reply needs to be sent with "finish review". Reply + resolve is such a common thing I do. It feels wrong to resolve before I reply (what if I don't finish the review at that time?) but "finish review" loses me my place & anyway if I do many comments I don't want to have to remember which threads to resolve.

Hey there, I am trying to use Graphite for the first time. I logged in with my personal GitHub account, which has organization access for my Work Organization. I installed the GitHub app in both my Personal Account, and the Organization (Work) and then there was a button that said

Join Team

So I pressed it, And Now my CLI access says I don't have access. I'm just trying to set it up for the first time and be able to use the Graphite CLI with my personal repos, and my work repos (Within the organization) but it says.

ERROR: Your team's Graphite plan does not include the CLI. To use the Graphite CLI in {Organization}, upgrade your plan at <https://app.graphite.dev/settings> 
ExitFailed:

There doesn't seem to be a way to leave the team that I joined - and as far as I know, I'm the first person from my work to try it. any thoughts?

In PR descriptions, applying strikethrough (

~text~

gets converted to rich text strikethrough) removes hyperlinks! 1. I'm not aware of any reason it has to work this way - I think you can just make the rich text conversion preserve links when applying strikethrough 2. Is there any way to use a pure markdown editor? It is trivial to do

[a ~strikethrough~ in a link](https://...)

when I run

gt submit

for the first time on a graphite branch, how do I disable the automatic opening of the related app.graphite.dev link in my browser?

hey all. really confused about something. we decided to try graphite so it would be easier for engineers to collaborate on features with dependencies. my expectation was that we'd all be able to see everyone's stacks in a tree view in the console and be able to easily browse what's in flight and see this locally in vscode as well. right now i can only see my PRs. can't see a list of my own stacks. and can't see the stack tree. feels like a fundamental misalignment between the app console and the value prop i saw in stacked diffs. can someone help me understand what i'm missing? i have found that i can make my own views but i have to ask people to paste links to their stacks all the time

My team has been trialing the Diamond AI pr reviews and I just want to confirm if I upgrade my steam from the core/standard plan to team we will get unlimited use of this tool?

I'm working on a stack of 10ish branches and I've CI optimisations turned on (see image). We run our CI checks on Github actions which charges you a minimum a minute for each run. We currently have 3 actions (unit-test, lint, integration-test) so if I restack on top of our main branch and submit then we'll be billed for 24 minutes (8 middle branches * 3 actions) of CI time that's useless to us. Are there any best practices here for how others have improved this?

Our merge queues are becoming very long, for example today it is 14 PR stacks long. Our CI is reasonable - between 10 - 20 minutes. It seems like the problem we have is that we work in a monorepo. What strategies can we use to deal with this other than splitting away from a monorepo (since this benefits us a lot)? Ideally we could have multiple merge queues and divide it out by folders, but this isn't currently possible

when I have a multi-branch stack, let’s say something like

main -> branch 1 -> branch 2

, and I merge

branch 2 -> branch 1

on github, I always end up in a state in graphite where it doesn’t see or properly sync that merge. After a

gt sync

,

gt checkout

displays

main -> branch 1 -> branch 2

instead of

main -> branch 1

I also see warnings during sync that look like this:

WARNING: Unable to clean up the following branches with merged PRs because their commits are not in main.
WARNING: Not operating on these branches and their descendants:
▸ branch 2
WARNING: To clean up these stacks, ensure main contains the merged PRs in the stack.

What am I doing wrong here?

Hey, is it possible to add Cursor Rules into the context for Diamond AI reviews?

For Merge Queues, am I supposed to be able to toggle this one if I use

rulesets

? The text mentions it won't be able to validate?

what's the rationale behind freezing diffs that i

gt get

? i'm bringing them into my environment so i can edit and collaborate on this stack. should i be doing something else?

hey all. co-worker (outside collaborator on github) said they weren't able to rebase or push changes to my diffs. but i am able to do that to his (org member, admin). what github settings do i need to change to allow them to modify my diffs?

Hi there, Can we use stacking and the merge all if we dont use graphite merge queue? Was looking at the plans and looks thats not part of the starter plan.

how do i run

gt submit

without opening the browser after? just want to make sure my stack is all up on github. not trying to walk through notes and PR or not