Hi Graphite team, I am running into issues enabling CI settings for merge queues. It keeps saying that the Github setting

"Allow specified actors to bypass required pull requests."

but I have made the graphite app exempt from the branch rules in Github....

me and my team are having issues with graphite having invalid authentication tokens, and not being able to log in to graphite update: seems to be ok now?

​*[Monitoring]*​ Graphite - GitHub is experiencing an outage. Some actions may be impacted. We’re seeing signs of recovery. We’re continuing to monitor our service health and GitHub's upstream status (https://www.githubstatus.com/) ​*Affected:*​ GitHub View incident button

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

how's this for a bug I purchased Teams yesterday I have the stripe receipt paid for the year. yet graphite still says im on the hobby plan and is still asking me to upgrade.! what the hells going on

please explain / fix this urgently!

Graphite is 403ing for me

our team isn't able to access.

Seeing the same thing for our team.

Web app is down for all pages. (PRs, inbox, etc.)

It seems to be working again, thanks for the quick fix! ty

​*[Resolved]*​ Graphite - Graphite Dashboard may not load This incident has been resolved. ​*Affected:*​ AI Reviews, Merge Queue, GitHub, Slack notifications, Dashboard, CLI View incident button

Am i unable to unlink a cursor account from my graphite account? it wont let me use agents because my cursor pro account is a different account.

I'm having the same problem as above ☝️ can't unlink cursor, it keeps saying I don't have a cursor pro account but I do

graphite doesn't load for me - it's stuck at blank screen

403 for one of the scripts

Homepage ui is broken again. same error page as earlier today. cc @Brett Bedevian

page-c39c3cc327293ed7.js:1
 Failed to load resource: the server responded with a status of 403 ()
webpack-87320c96066dc94d.js:1 Uncaught ChunkLoadError: Loading chunk 94432 failed.
(error: <https://app.graphite.com/_next/static/chunks/app/(routes)/%5B%5B...slug%5D%5D/page-c39c3cc327293ed7.js>)
    at i.f.j (webpack-87320c96066dc94d.js:1:18735)
    at webpack-87320c96066dc94d.js:1:1241
    at Array.reduce (<anonymous>)
    at i.e (webpack-87320c96066dc94d.js:1:1220)
    at c (29234-998f3aa19f5fd48f.js:1:188713)
    at 29234-998f3aa19f5fd48f.js:1:204608
    at t (29234-998f3aa19f5fd48f.js:1:206071)

Hey graphite team, Our team noticed that bug bot comments are all flagged as "Stale" despite being relevant in PRs and not stale at all. Is this something you're aware of and working on resolving? It's just a tad misleading. Thanks

Hey Graphite team -- We are seeing stacks that are showing fully able to merge even though only the bottom two PRs are approved. I can't find anything that would indicate why this is happening. I have looked at other stacks and they are requiring the approval but this one stack is green all way down (it is even ignoring open comments and allowing it to merge).

Organization names are case-sensitive in Graphite, but not in Github. "Official" name can be

ACME-Corp

, and Graphite will throw a not found error when directed to

<https://app.graphite.com/github/pr/acme-corp/{repo_name}/123>

Two bugs this has caused: • For some reason, Cursor redirects to lowercase version. When that happens, i land on the page seen below • After clicking "View on Github", github properly opens the PR (with the lowercase link). If I the click "View in Graphite" (through the Chrome extension CTA), it sends me back to Graphite with the lowercase version, and i get this error again. Can you make org names case-insensitive to prevent this?

minor frontend bug: when there are many commits, there are two scrollbars and they interact weirdly

Graphite has been loading PRs awfully slow for me for the last ~2 days and has given me an error quite a few times. Is there an ongoing incident?

I've noticed AI agents will run things like

gh pr checks 74 --watch --fail-fast 2>&1

. Unfortunately, this causes a complete waste of time when one of the PRs is not the root of the stack and the Github mergability check remains stuck on pending. This is annoying as a human too, since I sometimes have things notify me when ready.

I can no longer @ tag people for some reason in pr comments.

I created a PR and it says "Ready to merge", but when I try to merge it I get this error:

Request failed due to following response errors: - Repository rule violations found Waiting on required approvals from [team].

In github it does not say that it can be merged. This seems to be a bug on graphite's side, I would expect it to not say that it is "Ready to merge".

Getting this today. Is this a graphite or Github issue? My github seems to be loading fine

Hello team I have this pr app.graphite.com/github/…/2659 which has all the approvals and ci checks ready to merge but the but is disabled I have been facing with this issue randomly, I will merge using github but is there any bug reported about this? Thans in advance

Hello! We updated our gh SSO and it has seemed to break out connection with graphite. I have attempted to refresh on the settings screen but am met with an infinite loader. Can you guys help us?

Hey there, Since Monday (Sep 7) "Merge N PRs" no longer merges a whole stack for us. It merges the bottom PR, rebases the next one, then gives up on it in the same minute. The same kind of stack merged fully automatically on Sep 2 and Sep 4, with no change on our side (no merge queue, plain stack merge from the app). Timeline from Graphite's own "Merge activity" comment on PR #3839 in Tabflows/platform-v2 (UTC): - 21:52 "A user started a stack merge that includes this pull request" - 215305 bottom PR #3838 merged - 215334 Graphite rebased #3839 onto main (base retargeted via graphite-base/3839 -> main) - 21:54 "Graphite rebased this pull request as part of a merge" and, same minute, "Graphite couldn't merge this PR because it was not satisfying all requirements" - 215552 CI on the rebased commit finished green, GitHub reports the PR as CLEAN - 215954 the "Graphite / mergeability_check" run appears on the new commit (on Sep 4 it appeared 10 seconds after the rebase) All upstack PRs then get "couldn't merge this pull request because a downstack PR #3839 failed to merge". Same pattern on #3780, #3781 and #3785 earlier that day. For comparison, on Sep 4 (#3765 to #3767) the comment reads "rebased this pull request as part of a merge" and five minutes later "merged this pull request with Graphite", i.e. the job waited for CI, as your docs describe ("If the base PR in the stack has pending GitHub checks, do nothing"). So the merge job now seems to evaluate requirements once, right after its own rebase while the new commit's checks are still pending, and cancels instead of re-polling. In the dashboard the rebased PR shows "needs restack" for a few minutes, then becomes mergeable and I can click merge again. "Merge when ready" does not help. gt sync && gt restack && gt submit does not help either, the remote branch is already rebased. Break window: between Sep 4 20:02 UTC (last fully automatic stack merge) and Sep 7 20:14 UTC (first failure). Repo settings, unchanged since June: rulesets only, "Require branches to be up to date" off, "Dismiss stale approvals" off, 1 approval, squash only, required checks Prettier/Build/Lint/Typecheck/Test on GitHub Actions. gt 1.8.5. Is anyone else seeing this?

The UI for Graphite has been spazzing out a lot for me yesterday and today. It made me think something was broken with my monitor. I don't know if it's a useEffect going rogue and rerendering over and over or what. It doesn't happen every time, but I've seen it happen a couple of times. It even makes the menu bar area outside the browser window start acting weird. I wonder if there's some GPU access happening causing issues. This is on an M1 Max Macbook Pro with both the main screen and also when I have an external display plugged in.