File menu is missing a link to the file on GitHub. Sharing in #C02DRNRA9RA because the other links/options are mostly useless. • i almost never want to link to the file in Graphite's PR • i almost never want the raw versions of the file This is a disruption to my workflow most days because i often want to go through a file's history/blame or jump to a symbol it references. Thread in Slack Conversation

would be cool to have a toggle to expand all resolved comments in the UI. I find that i keep having to expand them so that i can see what the discussion was about and not comment on it again if i am satisfied with the response

things i miss from phabricator - 1. Hints on the "Merge PR" button. It would normally say "Ship It". but if it was Friday, it would be "Ship it? On a Friday?" and if it was afternoon it would be "Ship it? On a Friday? After 1PM". So some way to customize or set not blocking checks, but hints would be interesting. 2. Request changes was renamed to Return to Author, to make it less aggressive. I've considered making a chrome extension for everyone to install lol 3. When the PR is set to 'merge when ready', the 'Approve' button turned into 'Approve and Ship', and there was an option to approve without shipping if e.g. you had suggestions or questions but wanted the to be able to ignore you and ship it if they wanted

I'd like the ability to control dashboard sections for my entire org's team. It's not very easy to build some of the sections + i'd like to make sure we're all aligned.

💡 Make the MCP output in Claude less noisy

Would love to see the MCP tools more granular than

run_gt_cmd

such that we could disallow

gt submit

if we'd like to enforce manual review before pushing, rather than just relying on the LLM to listen to that request. That said, love that it's been released! Also, on https://graphite.dev/docs/gt-mcp

GT MCP is currently in beta and some workflows may not be fully supported.

is vague and could possibly use some detail, though of course one can interact with the MCP server directly for info on it's capability.

2 ideas: 1. Copy the "copy" functionality that exists in github (See screenshots) 2. Replicate "prompt for AI agents" that exists in CodeRabbit (also in screenshot)

Are there keyboard shortcuts available for the "pull from parent" buttons when creating a new PR?

Does Diamond know the location of file-based rules? It's awesome to see that Diamond now supports rules defines in checked in files! 🎉 I want to find out if an idea I have would would work... Problem There are some "localized gotchas" I would like Diamond to pay extra attention to. They're fairly trivial things, just easy to miss by a human and not possible to enforce with a linter or typechecker. Two examples: 1. In a

pytest

file which contains Python service fixtures, instantiate dependent services from scratch (using a shared DB session), instead of using their global fixtures. 2. If the content of an external-facing docs page changes significantly, review the frontmatter

description:

property of the relevant

.mdx

file. Solution I'm hypothesising Wanted to create a custom file-based Diamond ruleset for these gotchas, based on globbing a pattern like

*.diamondrules

. I wanted to start with a

/.root.diamondrules

file like this:

# What are `.diamondrules` files?

Files with the `.diamondrules` extension are used to define "localized gotchas" to pay careful attention to.

As an AI code reviewer:

1. Diligently follow the procedures described by these rules.
2. Apply these rules to files in the same directory as the `*.diamondrules` file, especially if it references a specific relative file.

And then we'd put write extra

.*.diamondrules

files as needed in each dir, for example:

# Maintaining consistent `description` Frontmatter property

Whenever an `*.mdx` file in this directory is modified, review that the `description` Frontmatter property matches the updated content of the file.

Some Qs: 1. Do you think this would work? 2. When you concatenate the globbed files, does the resulting prompt / tool call output also give diamond the location of each file? 3. Can Diamond look over the whole file when doing code review? In these gotchas sometimes context more than a few hundred lines away from the diff is important. CC @Alyssa Baum for thoughts

For suggested edits in Graphite (with Diamond), it'd be very helpful to be able to configure a pre-commit hook to be run. Devs on our team are reluctant to commit those suggestions because often the outcome is it violates a lint rule (or type check) that then result in CI check failure. Locally, our pre-commit hook catches this and prevents the commit.

I would love it if the Mac menu bar app could optionally be shown in the dock icon with a notification badge. I always miss when I have new PRs needing review because I'm not used to looking in the menu bar for a badge - most other apps show a red notification badge on the dock icon. Alternatively, if there was a way to access this metric via an API then I could vibe code a quick desktop app myself!

Feedback on new PR page: description placement is not 'visually centered' as it accommodates the PR details in top right 😅 i.e. it's literally centered in its 'column' in the layout/grid, but PR details are tiny and make it feel 'unbalanced' ⚖️

May I request issue tracking integration with Zenhub?

Any way to make the new PR page more vertically stacked? I don't always work on a large monitor, and the sheer number of horizontal panes make the diff I'm reviewing quite small on the center of the page

Can y'all make the right side pane sticky while I scroll down the description? Otherwise I get a bunch of blank space on the right when I scroll down long PR descriptions. It's also kinda hard to access the right pane unless there's an easier way to scroll back to the top of the page.

Is there a way to manually link stacks from different repos? I get graphite is built on top of the git history, and we have a few services spanning different repositories that we make changes to as part of a single piece of work / feature. It would be really handy to be able to link a commit / PR in one repo inside a stack of another for the reviewer to see all the changes in logical order instead of also needing to switch back forward between stacks. Not sure if possible but would be a cool feature to have

I would love to be able to provide an MCP to Diamond, so it can have more context on my projects

this is somewhere between #C06C4TH0D27 and "show and tell" ... i found the various icons in rows to be hard to see, so i made a little Stylus script to color the rows not super stylish, but does the job 🤠

Are there plans to add more tools to the MCP? It would be great for example to give references of PR comments to the agent

Make it faster! loading PRs takes ages... seeing the Graphite logo for some seconds then pr loads for some time then files take more time

The "new PR page" used to show HTML comments inline which was actually kind of nice. Now they're totally invisible. We use them in our PR template to describe what's expected in each section. Also, I enjoy the WYSIWYG editor in the new version, but having a way to switch to plain Markdown is table-stakes for a developer oriented product.

Is there a way to have Diamond run even for not published PRs? I want to address any potential AI feedback before I turn the PR over to other humans.

ah, that does sound right. i guess this is a feature request to ignore checks and perform the merge like i'm able to on gh's PR page then 🤠 Thread in Slack Conversation

refreshing my desire for phabricator/differential style

gt suggest

(add changes i've made locally after `gt get`ing somone else's PR as suggested edits)

For merge queue, adding schedules would be nice for automatic freezing.

Zed ide extension

extension for code review with diamond

Would be nice to have a cli subcommand to push all prs/stacks after a

gt sync

restacked them all ... having to iterate and push one at a time is no fun nevermind, thanks @Vampire for the lesson!

please 🥺 i just need to view a

blame

sometimes and the

raw

file doesn't cut it. it's super inefficient having to manually do like 5 extra steps to get to a file from graphite's PR page. i'd love if graphite just provided a link to the actual 'rich' file on github 🙏 ❌ not useful 99% of the time

<https://raw.githubusercontent.com/org-name/repo-name/12345commithash67890/path/to/file>

✅ useful constantly

<https://github.com/org-name/repo-name/blob/12345commithash67890/path/to/file>

Thread in Slack Conversation

It'd be nice if we could opt to use merge instead of rebasing for restacking.