I have 4 threads in a PR, 2 resolved 2 unresolved. The problem is, one of the unresolved ones is outdated. Due to that it is nowhere shown except on the threads view. Clicking it there does nothing if you look at the latest version. If you look at a previous version and click it, it says that this comment is only visible on latest version and suggests to switch to it, which then of course does not end up at the comment and just provides the previous dialog wrong. In the IntelliJ PR integration in the timeline I can still see the comment and click "Resolve", but it does not do or change anything either. So besides that the dialog lied at me, outdated threads should probably either count as resolved or be their own category but not show as unresolved even if they technically are. Hm, now I was able to find and resolve it in gt web. But still strange, especially as I couldn't navigate to it from the threads view.

Attempting to add a teammate to the reviewers of my PR and received this error. Added them successfully through github web app. They are a graphite user. No blocking issue just wanted to report for visibility.

Images in the docs are being stretched and not maintaing their aspect ratio correctly

Some revisions are twice or thrice in the list of versions. I could understand if you push one revision, then push a different revision, and then push back to the previous revision. But the versions are one after the other. Sometimes even with different times. This looks either like a bug or at least like a missing feature that those should not make separate versions. Attached you see an example from https://app.graphite.dev/github/pr/typesafegithub/github-workflows-kt/1603/feat-abg-provide-untyped-fields-always-and-typed-ones-if-type-available

I have a 17 PR stack. The first PR was merged. Then I found that I should add one PR between 1st and 2nd PR. So I created a new PR from trunk, moved the remaining 16 PRs onto it using

gt move

. I expected or hoped for an 18 PR stack with the first PR still merged and 17 upstack PRs. But what I got was a new 17 PR stack with the new PR bottommost. 😞

I’ve been facing lately this message on my OSS project and not sure how to debug this. Is there any way I can see a better message, log or something to understand what is going wrong? 🤔

graphite seems to create some kind of temporary branches like

graphite-base/73

. sometimes they don't get removed and linger on.

Sometimes when i run

gt get

(even with the

-f

flag), my local and remote still differ (i can see the commit SHAs are different). Any ideas how to remedy this, i.e. if I just want to get my local stack in the exact same state as the remote? Happy to send logs!

Hello, is graphite down / working very slow? My team reported it to me, I tried reloading my dashboard and it got stuck loading the PRs

​*[Identified]*​ Graphite - Graphite partial outage We are continuing to work on a fix for this incident. ​*Affected:*​ Dashboard, CLI View incident button

​*[Monitoring]*​ Graphite - Graphite partial outage We implemented a fix and are currently monitoring the result. ​*Affected:*​ Dashboard, CLI View incident button

https://app.graphite.dev/github/pr/CondorSoftware/condor/4109/Renamed-CondorUserSerializer-to-DummyUserSerializer-since-we-don-t-use-it-because-of-user-being-unique#comment-PRRC_kwDOHlaxHc5nNyjj Clicking the resolved comment from a previous version does nothing, regardless of whether I’m in

Threads

or

Activity

Not sure that this is a bug but the behavior seems different than what I remember it to be.. I have a stack where all but the non-base PR are still awaiting graphite

mergeability_checks

. IIRC, the graphite

mergeability_check

should pass as graphite is fully aware of the whole stack. Because I'm still waiting on this check, that now says it will only pass when downstack PRs merge (Ive tried

rerunning all jobs

in graphite UI to no avail), I cannot

Merge stack

in graphite, only check

Merge when ready

. Am I doing something wrong or misunderstanding the intended workflow?

Hi, my ability to submit stacks via the CLI has been hampered pretty hard the past couple days. Other commands like sync/restack, etc are all fine, it's just submitting. Details in thread.

I'm experiencing issues with the "publish all PRs" button when editing a stack -- its been a bit unreliable... I tried it a few times w/ the same stack, and it only published a few of the PRs (all were in draft mode).

We had a similar problem when we used to use Sourcery’s auto-reviewer, but now it’s self-inflicted. The PR should not be struckthrough if it’s reviewed by a bot, especially Graphite’s own bot.

Having trouble setting up vscode extension. I'm using the CLI fine now but seeing this in vscode. Refresh isnt doing anything, and not sure what to do with

try manually specifying *Graphite: Command Path* in your VS Code settings.

The VSCode extension is broken on windows. It tried to run

gt.exe

but the graphite command line is installed as a powershell script

gt.ps1

... Has nobody tested this??

Overriding the CLI to

gt.ps1

made it get further, and now it's stuck showing a loading spinner, no errors in the output window

on reloading I get the error:

fatal: not a git repository (or any of the parent directories): .git\n

When using the CLI with

gt create --ai

the branch prefix configuration is ignored if it's configured to only add the prefix to generated branch names

I’m unable to comment

I am getting this message on the dashboard, even though I have given the required access to the Graphite app on Github.

The Graphite GitHub app is missing permissions for my_github_org/repo_name, update settings to enable real-time data

I merged this pr as a stacak via the UI, but it didn't seem to do it the way it usually does. This PR never went into my "waiting to merge" PR category, and now has merge conflicts against the trunk branch 😕

Hi! Learning the tool and it's great so far, but I've got one thing Im a bit stuck on. We're trying to get 'merge when ready' to work on our team, but we've got commit signing enabled. I've gone to the proper page on the settings, gotten the GPG key, added it to github, but it looks like Graphite isn't picking up that it's there or something, because I still can't use the merge feature on graphite.

I've gotten this empty error message a few times when trying to submit different branches:

ERROR: Failed to submit PR for 08-29-mlops-4079_log_position_eligibility:
{}

gt r

uses

--allow-empty

. I'd greatly prefer if it did not. Even with the forked-pr support is not there yet, I use

gt

to bulk rebase multiple PRs or also stacks I submit individually. If a PR is merged I usually rebase, see that the PR branch is pointing to the same commit as the trunk branch. This way I can sure the changes are all applied properly, and I can safely delete the PR branch. When using

gr r

I still see a separate commit, it is just empty. 😞

Every couple of minutes while working on a review, the page is "jumping" randomly, scrolling me somewhere that i wasn't. It happens when I'm just sitting still, scrolling, or writing a comment. Super jarring.

Kinda buggy experience from a teammate leaving: • Graphite shows that user as still present on GT Web UI even though they are off the github and that should probably propogate. • Mystery failures when trying to land diffs they accepted (when in reality GH merge was failing because it didn't have a required review) - but graphite still shows it as successfully reviewed

Is Graphite down? Received the following error

ERROR: Your Graphite auth token is invalid/expired.

Please obtain a new auth token by visiting <https://app.graphite.dev/activate>

and https://app.graphite.dev/activate returns 500