The only big big piece of feedback I have is that the stacking of the main views is super unintuitive, specifically how they animate. I mocked up an alt

This message was deleted.

This message was deleted.

This message was deleted.

made this channel public. Any member in this workspace can see and join it.

Hi All, we’re starting to play with

Graphite Protections

, received this message after a protection is created. However, unsure where in Github to apply this setting to prevent merges from Github. Any pointers on this?

Hi - we're getting started trying to use Protections and found ourselves unable to express what we want. We are looking to have a file owned by a team, and always require that file to be reviewed by someone on that team who is not the author. When we use file owner, the check always passes because there is no way to exclude the author. We tried coming up with an alternative by wanting to require at least 1 reviewer from a list of people using the number of required approvers feature, but it seems like there is no way to write (at least X people from this list/on this team). Any ideas for how we could solve this?

Graphite Protections

Apply to all PRs

does not apply to all PRs. We have a

Release Manager Approval

protection that applies to all PRs. It simply requires an approval of a release manager for every PR. But the rule is N/A as seen in this PR status.

Whoever thought about and designed/implemented this comment jump in the scrollbar is chefs kiss Fantastic idea!

Graphite reviewer hasn't made any comments on any of my PRs yet, so I tested out an easy case, and it still found no issues. Not sure if this is a bug, or if it's just ridiculously conservative 😄

I have received the invitation to enable Graphite Reviewer in our repository; however, the user interface appears to be preventing me from doing so. The "enable" button stays disabled even after selecting the repository for which I want to activate the Graphite Reviewer.

I applied to join the Protections beta a few days ago and haven't seen any response - how long does it normally take?

For Graphite Reviewer, is it possible to have the reviewer only review published PRs, and not review draft PRs? A coworker found the comments on his rough, work-in-progress draft PRs distracting.

Does Diamond respect

.github/copilot-instructions.md

?

Is it possible to exclude certain folders so I don’t get this error?

Does

Write for me

respect custom Diamond instructions?

We turned Diamond on yesterday. One piece of feedback I got today: it would be nice to be able to get Diamond to run before a reviewer is assigned so that they don’t get the early notifications. Our setup is to automatically assign PRs to one code owner, and Diamond doesn’t run on draft PRs, so the only way to get the AI review is to publish the PR, which assigns a reviewer so they will get the extra notifications. Not a major problem, but I figured I’d share.

We use both Diamond and Github’s Copilot reviewer. One issue we run into right now is that there’s no way to request a review from Copilot from the Graphite UI. You have to jump to Github to do it.

Diamond is repeatedly misstating how nested list comprehensions work

What does it mean for MCP to be in the CLI? Do I have to “register” it as an MCP server somehow, or will Claude Code just pick it up by the existence of the CLI?

FYI

This is part of my

CLAUDE.md

, almost like a “mini-MCP” for Graphite:

### Graphite Workflow

\`\`\`bash
gt c -am "message"    # create a new branch containing all changes
gt s -mp              # submit with publish + merge-when-ready
gt m -acm "message" && gt ss    # modify and submit branch with a new commit containing all changes (for fixes/lint)
gt log --stack        # view stack status\`\`\`

**CRITICAL**: For fixes, lint, formatting, etc. on an existing branch, use `gt m -a` to modify the current branch instead of creating new branches.

Hi, how do I use the Graphite MCP with another service? In this case, Devin.

FYI i just turned off graphite chat. the fact that it would open little popups in the bottom right of PRs with suggested questions was really annoying. feels like growth hacking over actual user value

Customize your PR descriptions, with ease. No Markdown needed.

Will Markdown still be supported? As a keyboard-only user, I find it significantly better than rich text editing.

When checking the https://graphite.dev/blog/graphite-merge-rules blogpost on how to get into the protections beta, I found the google forms to be a dead URL. I would really like to be added to the beta, is there someone who can help me out?

Bad suggestion. It duplicated the next line after the deleted line.

in the “submit review” input field, I’d like to have cmd+U or cmd+shift+U to start the upload of a file like we can in many other tools (Superhuman, Linear, and Slack come to mind)

on the new PR page, the floating comments are really bad for reading code suggestions because they’re all squeezed into a narrow pop-up

The new markdown/comment editor is a big step up so far - great job on the refinement, Graphite friends.