Hi - how do I change the organization linked to my graphite account? I tried graphite a long time ago with my old company and am trying it again now with a new one - but the old organization is linked and I can't seem to change it.

How does everyone deal with review staling? See also: https://github.com/orgs/community/discussions/57513 Recently, whenever I start to merge an entire stack, I have to pause between each PR to ask for feedback again, because GitHub has dismissed the review (because the base changed)

Is there a way to create a section in the web ui for pull requests that haven’t been assigned a reviewer yet?

how do i only submit the current branch? i'm collaborating on a stack and i see some unexpected changes downstack, i don't want to mess with somebody's stack

Is there a graphite command to take a stack and close all its branches on the remote, thus allowing it to be restacked and submitted once more? (GTI user here, I'm missing some CLI knowledge)

how do I make a PR request on the original repository from a branch on a fork (or is the only way of doing this authenticating graphite with the original repository?)

Two questions: • Is there a quick way to open a PR in GitHub from Graphite? In GitHub there is the “Open in Graphite” button, but it seems in Graphite there is the option to “Copy link to GitHub” but this is a lot less convenient than just middle clicking an “Open in GitHub” button • Is there a guide/blog anywhere from the Graphite team on recommended practices/best practices for CI/CD setups when using trunk-based development? I’m asking because of the (seemingly common) issue of CI minutes and also trying to work out how to best optimise our CI/CD but couldn’t find good examples anywhere of setups used

Hey, I keep getting

🌲 Pulling staging from remote...
staging is up to date.

ERROR: Received invalid dependency response

When running

gt get <branch>

. How do I solve it ?

Hey, just attempting to test out graphite on our project. Two issues Issue 1: I am getting a permission warning. (image 1) Permissions are presumably already set: (image 2) (image3) Issue 2: Is graphite vs-code extension on WSL supported? Getting a loading spinner (image 4) (log in thread)

I would like to check if a repo already has been initialized via Graphite within a script, is there a command already in the CLI to do that? Or am I best off searching in the

.git

directory for

.graphite_repo_config

?

Hey, I want to set default labels that are always added to my PRs, is there anyway to do that? Or maybe being able to pass them in through the CLI?

How do I delete already submitted branch from graphite web ui? What I did is: 1. Created stack A -> B -> C and submitted it 2. Folded B -> A, Now, on local B branch disappeared, but in the web ui there is still B as part of the stack..

Hi folks, I have a few questions WRT merge queue 1. Is the reason you recommend Squash & Merge strategy you want to force a Rebase & Merge behavior even if a team is not following a one commit per PR workflow? 2. About the fast forward merge. What exactly does it mean that CI is ran in parallel for a stack of 3 diffs? a. Option1 (3 parallel ci runs) i. A single CI run for Diff 1 ii. A single CI run for Diff 1 + 2 iii. A single CI run for Diff 1 + 2 + 3 b. Option2: (a single ci run) i. A single CI run for Diff 1 + 2 + 3 c. Option3: other? 3. Submitting a PR stack to the merge queue is an atomic operation correct? Either the entire stack is merged, or the entire stack fails. This applies to Timeout scenarios as well? The entire stack will be taken out of the queue 4. Before using the Merge Queue I used to be able to use admin privilege to bypass one of the requirements (having the PR be approved). I tried this again with the Merge Queue and it failed. Have I lost this capability permanently?

How do I make a “prequel” to my branch? i.e. I have a bunch of changes and an existing PR. I want to split it into two branches, with the new one coming before the existing PR, since it has relevant discussion on it.

How do I fix a stack that has commits from a stack under it I might have messed up some command :’)

hey folks how do i see all the stacks that are based off a release branch? for example i have master <- release branch <- 1st stack of PR master < - release branch <- 2nd stack of PR at the moment i can only see the latest stack that is pushed based on release branch

I have recently switched to using the graphite app for code reviews and I am really enjoying it for the most part. However, I am struggling to find an easy way to view all uses of an entity. For example, I want to search code changes for all references of a variable or method name. If I control-f it seems to have a browser search override that does not include collapsed files. And even then it doesn't always work, I presume from lazy-loading perf. I can't find anything obvious after searching help docs + slack. So I am looking here to see if anyone has recommended patterns. Is there a way to search all code diff of a pr? If not, Is there a way to toggle all files between open and collapsed?

👋 Is it possible to prevent triggering workflows for all PRs in a stack when a re-stack is made, to avoid queuing multiple builds unnecessarily? I'm currently using empty commits to trigger the builds

I've started getting

Your org has enabled the Graphite merge queue for merging into main

comments on my PRs even though I'm authenticated and Graphite works fine, is there a way to fix this?

Hello, I would like to know what our active stacks are. I see from previous questions that the current recommended method is to PM hardworking Carissa Jansen. Noting here that she is getting more work 😄 .

Hi there, how do I view all of the Graphite history? I am running into a situation where my changes were completely deleted in a mid-stack PR when I merged all PRs in a stack. I can't find the commit in Github anywhere, and Graphite has already deleted my local branch. When I look at the Graphite version history, the version where I expect to see the changes is showing a different change.

I think the answer is no, but is there a way to include images in a PR description via the CLI? (Ideally something that can handle the upload+hosting, like dragging/dropping into the Graphite UI does)

Is there a way to disable the comment Graphite puts on pull requests showing dependencies if there's only one branch in the stack?

Hey folks asking on behalf of a colleague, how do we sync this gt comment after prior branches are merged

In addition, is there a way to show the graphite comment as part of the PR description rather than a comment so that the stack is more obvious to reviewers?

What’s the difference between

gt get

and

gt sync

? I read the documentation but I’m still unsure of the difference. In which situations should the commands be used?

Can I reset my sections somehow? I'm an early adopter and it looks like newcomers have slightly better tuned sections (e.g. I don't have "Returned to You").

In the configuration page you mention an user-level configuration for the rebase behavior? Where is this configuration set?

gt config

doesn't seem to have that option. https://graphite.dev/docs/configure-cli

How can I pull the previous version of a Graphite PR? I see the commit hash. Maybe it's already been garbage collected on the remote, because I can't do

$ git fetch --depth=1 .  09491a0921749a8674112a55238210ea6e7ff6cd
fatal: git upload-pack: not our ref 09491a0921749a8674112a55238210ea6e7ff6cd
fatal: remote error: upload-pack: not our ref 09491a0921749a8674112a55238210ea6e7ff6cd

but Graphite can still show the diff.

Hi, I'm seeking a seamless integration between our Jira board's ticket statuses and our Graphite metrics, specifically aiming to display related Graphite Pull Requests (PRs) on the corresponding Jira tickets, even when they're connected to subtasks. In our envisioned workflow, as an example, when an engineer progresses a Jira ticket from 'Open' to 'Needs Review,' then 'Needs QA,' and finally to 'Ready for Regression' following successful end-to-end testing, is there a method or integration that ensures these status changes in Graphite automatically reflect in the Jira tickets and that the Jira tickets get automatically moved on the jira board status? The ultimate goal is to establish an integrated system where status transitions in Graphite trigger automatic movements of associated Jira tickets, ensuring that the relevant Graphite PRs are visible on the respective tickets, including subtasks. Seeking advice, tools, or best practices to achieve this level of integration, where changes in Graphite metrics seamlessly prompt automatic updates in Jira ticket statuses, providing a synchronized view within our development pipeline. Thank you for any insights or recommendations!