hey just a heads up that the new version of

gt

is very unreliable when it comes to syncing the state of a local branch to remote. it used to work just fine and now i’m constantly running into issues. often branches that get merged don’t get correctly closed. additionally branches that get merged into other branches throw

gt

into a state of chaos whereas before it knew it needed to fold the branch. anyhow just in general not enjoying this update whatsoever

I can't submit an empty PR with the CLI. I want to do this to create a pr preview link to give to people, which I can keep moving to be on top of the stack as I do more things. To unblock, I can make a no-op change, but it probably should let me do this (after properly warning that the PR is empty, which it does 🙂 )

The VSCode extension often times does not show all conflicts to be resolved, but marks the "continue" button as available (which then fails). In that case, I need to run

git status

, and fix all remaining files manually, then do

gt add -A

and then "continue works again". Very weird behavior.

The

--show-delete-progress

of

gt sync

is kind of wonky? (I just tried this option out of curiosity, this is not an important bug report)

Strange behaviour when scrolling up in a diff using the

K

hotkey:

Small bug: whenever I click a link from the graphite slack bot, it opens the website twice

It seems like suggestions in comments aren’t showing up correctly:

Getting this quite often when the remote branch didn't actually change:

There have been remote changes to my_awesome_branch.
Check out the branch and run `gt get`, then try submitting again.
To overwrite remote changes, use the use the --force option of gt submit.

I have been sticking to the legacy aliases and using

gt rs

though- could that be why?

Recently I faced twice an issue when using `gt get my-branch-name`: the command succeeds and I get the right branch checked out but it’s not tracking the remote. If I then do

gt pull

, it says:

There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> my-branch-name

Then, if I run

gt track

it says:

my-branch-name is already tracked.

Am I doing anything wrong?

In the web review UI, if there are unresolved threads shown on the right, and the file that the thread is in is marked as "viewed", clicking on the thread does nothing. This is very confusing, especially since the file tree is hidden by default. The thread marker does show which file it is, but I need to either scroll through the PR and find it (and realize that this is even the problem), or go to the file tree on the right and click the right file (which at this point I don't even see the name of anymore). It would be a lot more intuitive to me, if clicking an unresolved thread just opens the file that was marked as "viewed" and takes you to the thread.

Whenever I try to

@coworker

in a comment box, it doesn't work if I don't have a space preceding. This happens often when I add a comment, and then edit to tag someone, or if I try to

@coworker

in the middle of a sentence. It's not terrible, but I run up against this friction maybe 5 times a day.

image.png

^ Context - we adjusted an S3 configuration on the bucket that hosts our single page application. The configuration change broke our static site serving. We immediately reverted the config change, which appears to have resolved the issue immediately. Thank you to @Brendan Ngo for the extremely fast fix 🙂

does anyone else experience slightly laggy scrolling when reviewing medium/large sized prs on safari? wonder if this is just a "safari bad" situation or if it is something that can be fixed. dont have this issue for github or much else on the general web

oops, the docs.graphite.dev redirect is broken. maybe related to the 404 above but a different domain here

Escape regression! I was typing a comment and hit escape and it threw away the comment without prompting.

if a file is collapsed, then clicking on a comment in the sidebar does nothing. i would expect it to un-collapse that file and take me there!

Small thing, the hover indicator in a line can cover up code. Maybe making it 80% opacity would help. I misread the code and thought it was a typo until I happened to move my cursor.

When I try submitting a stack from the CLI I get the error:

ERROR: Your Graphite auth token is invalid/expired.

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

However, when I go on the site and create a token, it vanishes when I refresh the page, and using the new token on the CLI still throws the same error

hi, i’m again having lots of issues with graphite. now for some reason it’s saying that my branch is empty, even though the data is clearly different. 😞 none of this was happening prior to the v1 update

Merge when ready doesn't always seem to work—I had a PR that was green and ready to go but Graphite kept flapping between "Waiting for CI" and ready. Feel free to DM if the PR URL would help.

Hey! Im new to graphite, but i love the new way of handling PRs! The vscode extension is bugged on windows 😞 On the logs i can see that its looking for "gt.exe", but when you install the cli via npm, it creates those files (see screenshot). Fix: change "gt.exe" for "gt"

Not sure if bug report or feature request:

gt submit

seems to swallow the

pre-commit

logging of pre-push hooks. Specifically this:

Running formatting (~30s).......................

Because it's a longer running hook, it makes it look like graphite is hanging on

:incoming_envelope: Pushing to remote and creating/updating PRs...

and I don't want my team's new graphite users to get stuck on this 🙂 If the hook succeeds, we don't get any logs when doing it through graphite, though we get the info with raw git because we have the hook with

verbose: True

If the hook fails, we get the entire logs of the hook in red (harder to grok than normal) because it's error output from

ERROR: Command failed with error exit code 1:

We're in a bizarre situation where none of the

gt

commands (e.g.

gt init

) generate any stdout output except for

gt --version

and

gt --help

. The

--debug

flag does not help. There is no stdout output telling us where the log file is. Based on other machines, it should be in

~/.local/share/graphite

, but there is no

graphite

dir there. We tried Graphite version

1.0.9

and

1.0.10

, and this is on node version

v18.18.2

.

Can’t merge due to invalid JSON

Hi. I am new here and relatively new to Graphite. Since this morning I only get a "Sharpening pencils" message. I tried to clear the browser cache, but that didn't help. Other engineers in the org do not appear to have the same message. Any advise would be appreciated. Thank you

have noticed that sometimes i'm missing diffs in my review inbox! not sure why, they're all in the same repo

Hey team, could we get the regex improved to ignore more code generated patterns? We have a lot of Go code gen but it still shows up as a change, making the initial view of the PR very noisy. Each file has one of the following header comments:

// Code generated by ent, DO NOT EDIT.
// Code generated by protoc-gen-connect-go. DO NOT EDIT.

Hi, we are in a situation where a whole stack is approved and we can only merge one PR at a time Each time downstack is merged, it dismisses the immediate upstack approvals thereby making all unstack unmergable unless we reapprove again. Our merge criteria is that PRs requires 2 approvals (and at least one code owner approval who is our QA engineer). Is this the expected behavior? Can someone help with this please? The desired behavior is that if a stack (regardless of size) is approved, we’d like to the whole stack to be merged together.

Hello! Graphite seems to have broken locally for me:

gt ls

, or any graphite commands don't work with the exception of

gt --help