This message was deleted.

What you're describing is something akin to an "integration branch" in a lot of orgs. We're using an integration branch at work right now. To make all graphite stuff point at branch, I used

gt init --trunk

to set my trunk to the integration branch (that would be

freeze

in your case). Can't really use the Graphite web app to merge things like i'd expect (i just use GH for merges), but i can use the CLI to get work done and that's what counts. YMMV, i'm still new to graphite.

@Matthew Hokinson we're working on better support on the web for cases like this in the new year. Thanks for the detailed report -- it will be super helpful for our work here! As Tyler said -- are things clearer on GitHub?

@Jacob Gold Thanks for the tips. Setting the trunk branch to

freeze

is the closest I've gotten, but this still causes issues with the web interface. Sounds like there isn't a way around this though, so for the time being, GH is fine to manage merging the PRs. @Tyler Nieman have you had any issues with merging each PR manually through GH messing up the Graphite state? I saw there are failing GH actions (screenshot below) which check the parent PRs of the stack for merge status, but those can be ignored without fear of borking Graphite I assume.

I haven't, but I manually run

gt sync

on my local env after merging into the "integration branch" via GH EDIT — oh, that's the github action. there's a related thread, lemme get it...

Gotcha, that's what I've been doing as well. Seems to be working alright so far 🙂

aforementioned related thread about the graphite gh action showing "failed" https://graphite-community.slack.com/archives/C02DRNZELUU/p1702488631927539 someone from Graphite contacted me directly to turn it off for our org since it was making every PR look liked it failed

👀 if there's not a way to do this already, would it be possible to get this disabled? I'm facing the same issue and about half my team is still using GH, so the graphite mergeability failures are creating a lot of false positives

Taksh turned it off for our org — they messaged me after i made a comment in that original thread.

Ah ok, sorry think I misread that, Thanks for the info!

@Matthew Hokinson you can disable the check by going to settings -> organization