Hi team, I was invited by my team on Graphite, but I am not able to join. As soon as I click on 'Join Team', I get this error. Any idea what might cause this?

I used to see this pop up more often (many months ago). I haven't had the problem in several months now, but working on a stack with a coworker, I have a local change I'm trying to submit but graphite says there's a remote change. But when I try to

gt get

or

gt sync

to resolve, nothing is resolved, my local change is not pushed, stuck in circle 2 questions I guess: • how can I avoid getting into this state (understand the remote changes thing will happen, but this endless loop / circle is what I'd like to avoid, curious if there's some specific process/flow that's causing it?) • more pressingly, what's the best safe path to resolve? I don't think the

--force

option is super risky in this case since coworker and I are working on different areas, but is that the best way forward?

zsh: ~/code/my-project> gt submit --stack
🥞 Validating that this Graphite stack is ready to submit...

ERROR: Branch feature/my-feature has been updated remotely. Use gt get or gt sync to sync with remote before submitting (or use the --force flag to override this check).
zsh: ~/code/my-project> gt get
🌲 Fetching branches from remote...
Running git fetch: [========================================] 100% | Done
main is up to date.

🔄 Syncing branches...
Branch feature/my-feature is up to date with remote (PR #4846 v29).

🥞 Restacking branches...
feature/my-feature does not need to be restacked on main.

Already on feature/my-feature.
zsh: ~/code/my-project> gt submit --stack
🥞 Validating that this Graphite stack is ready to submit...

ERROR: Branch feature/my-feature has been updated remotely. Use gt get or gt sync to sync with remote before submitting (or use the --force flag to override this check).

EDIT: Just submitted CLI feedback named

jon-stelly-bug-report

. Let me know if you need more info, not sure if the cli debug log is enough

I keep getting operations erroring on "error: cannot lock ref 'HEAD': Unable to create '/Users/matt/src/llvm-project/.git/HEAD.lock': File exists." and git gc is apparently holding the lock. Is there a way gt can surpress gc before it begins an operation so it won't be interrupted

I'm not seeing the PRs from a repo although I've synced it

I think this is a bug. I hit merge on a PR (though I cannot remember if I did it in Graphite web UI, Github or the Slackbot) and the Graphite bot messaged to say it failed to merge, but it did merge. Any idea what's going on here?

hello, I think we’re seeing a bug with upgrading the free trial to a paid subscription. I upgraded and when I click “Manage billing” I see a receipt for our annual subscription. it previously said the trial would auto-convert to paid on June 16, but that has passed and now it says it will auto-convert on June 23. I’m unclear why that date changed and whether the upgrade registered - especially because throughout the UI, plugins and CLI, our team still sees the banners that our trial will expire. can someone help take a look?

Hi, we cannot leave comments in github PRs

Hi, I'm not able to submit my stack and I'm not sure why, I keep seeing the following:

📨

Creating/updating PRs...

ERROR: Failed to submit PR for 06-17-reorganize_repo:

GitHub returned an error: Pull request not found

and:

ERROR: Error response trying to pre-submit PRs: 500

​*[Identified]*​ Graphite - GitHub is experiencing an outage. Some actions in Graphite are affected. We're continuing to monitor the situation. More information can be found on the GitHub status page: https://www.githubstatus.com/ Note: repositories hosted on-prem using GitHub Enterprise Server are not affected. ​*Affected:*​ GitHub View incident button

​*[Resolved]*​ Graphite - GitHub is experiencing an outage. Some actions in Graphite are affected. This incident has been resolved. ​*Affected:*​ GitHub View incident button

​*[Investigating]*​ Graphite - Graphite app is loading slowly for some users We are currently investigating this incident. ​*Affected:*​ Dashboard, CLI View incident button

​*[Monitoring]*​ Graphite - Graphite app is loading slowly for some users We implemented a fix and are currently monitoring the result. ​*Affected:*​ Dashboard, CLI View incident button

​*[Resolved]*​ Graphite - Graphite app is loading slowly for some users This incident has been resolved. ​*Affected:*​ Dashboard, CLI View incident button

I'm using the dismiss-stale-approvals gh action and it seems to be dismissing approvals when graphite merges a branch into main, usually due to the commit message changing? I'm a bit confused by this

We're seeing a bunch of cases across our team where Graphite's Slack integration reports that a PR failed to merge, but actually it merged successfully

Hello! last time I was here was more than 2 years ago with another company. Glad to see you are rocking it! I have a NTH request, not a bug per se but something that is not very efficient When you push a PR it runs CI, once you add it to graphite merge queue it will run CI (even if main branch didn't change since last CI) maybe something could be done to skip that extra CI?

Maybe not exactly a bug, but the merge queue not actually “merging” PRs on Github also has the side-effect of making release notes broken. Github has an API you can use to generate release notes for a commit range. It lists merged PRs as well as contributors on a release. We use this as our changelog on deployments. Since we enabled the merge queue, it now only picks up PRs that were actually merged in Github. Would Graphite consider a “true merge” option? One way I can imagine this working is by merging down PRs from the top of the stack into their parents until it finally merges into main. This would also restore things like Linear merge triggers.

UX bug: the checkmarks and chevrons look really similar to each other in the Graphite VS Code extension

Not a bug report, but I have a question about - https://graphite.dev/blog/startup-program-announcement, where is the best place to direct that? Thanks!

consistently seeing "failed to merge" in Slack and it's wrong - it actually is successfully merged. have seen this at least 5 times in the past week.

been running into the same QOL issue here where branches can't be detected by some common CI tools. it's the biggest pain when the PR is already on main and re-running CI doesn't fix. sample logs

Run dorny/paths-filter@v2
  ...
Get current git ref
  /usr/bin/git branch --show-current
  graphite-base/2837
Changes will be detected between main and graphite-base/2837
Searching for merge-base main...graphite-base/2837
  /usr/bin/git show-ref main
  /usr/bin/git show-ref graphite-base/2837
  <COMMIT_SHA> refs/heads/graphite-base/2837
  <COMMIT_SHA> refs/remotes/origin/graphite-base/2837
  /usr/bin/git fetch --no-tags --depth=100 origin main graphite-base/2837
  fatal: couldn't find remote ref graphite-base/2837

https://graphite-community.slack.com/archives/C02DRNRA9RA/p1746037355585019

Hello, been getting errors on Graphite being unable to merge branches even though it succeeded

Search in a diff has become broken for me by the search box being defocused every time it scrolls to a result, so I start typing and get kicked out of the text box after approx. every key press.

we can't submit comments or mark files as viewed when in the "Potenatial merge commit" version view

Not 100% a bug but the biggest problem in our company these days: The app is consistently really slow. Even small PRs take long time to load and larger PR stacks often take long enough that folks just open github in the meanwhile and start reviewing. What are the plans to make the review UI more snappy and load small PRs more or less instantly?

Hello, I cant get the VSCode extension to load. It had been working for months and last week (probably related to a MacOS update) it stopped working. I have tried uninstalling and installing again graphite through Homebrew, I can access the CLI from Zsh without a problem; but somehow the VSCode extension is unable to locate it. Ive tried manually specifying the command without success. I have tried the run bre installation button and I get the second error on my screenshots. What am I missing?

I folded this stack into three PRs, but I still see four on the web

Hi, I'm trying to sign up for the Graphite Core free trial, but when I click "Start free trial", I'm redirected back to the home page and nothing else seems to happen.

Hi Graphite team! We've been having some issues with the Graphite Slack integration notifications - attached a video below (clicking the graphite notifications does not clear the notification count compared to other notifications). Let us know if this is something you can repro/fix on your end (could a Slack issue as well) - really appreciate it!!

I don't think this is a bug, but the way Graphite is not that compatible with a Monorepo(Turbo repo). Team of 8 engineers. 5 packages in our mono repo. Merge to master happens 3 or 4 times a day. GHA cache is immutable, scoped and doesn't share artifacts between branches. That means that every time you ask Graphite to merge a big PR stack, it will duplicate your PR stack creating it's own PRs, with 0 cached layers and it will take 25-30 minutes for each of our PRs there. This also means that it will flood the cache (that's limited to 10GB) with 1.6GB worth of entries and will evict important and older entries (like from

master

) and will make the CI fail due to this. This became an issue after we moved to a Mono repo and we saw our cache entries grow larger and larger. Any plans to change the way this works, or suggested work arounds?