mcintyre1994 3 days ago

This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I doubt we'll want to keep relying on that for very long now.

▲

dbalatero 3 days ago | parent | next [-]

You can still think of AI as one facet of Graphite's product that you can use or not depending on your work style. Stacked PRs are still a core piece and not going anywhere :)

	▲	victorvation 2 days ago \| parent [-]
		Except for the undismissable "Pay use more to enable AI reviews" nag that Graphite places above your CI checks and assigned reviewers.

▲

WXLCKNO 3 days ago | parent | prev | next [-]

Never heard of graphite before today. Were they built specifically for AI code reviews or it's a pivot / new feature from a company that started with something else?

	▲	David 3 days ago \| parent \| next [-]
		No, they've been doing "managing stacks of dependent pull requests" for a lot longer than AI code review. I've mostly been a happy user, they simplify a lot of the git pain of continually rebasing and the UI makes stacks much easier to work with than Github's own interface.
	▲	mcintyre1994 3 days ago \| parent \| prev [-]
		They started as a better PR review tool, with the main feature that you can stack PRs that have dependencies on each other. It solves the problem of having PRs merging into other PR branches, or having notes not to merge something until another PR merges. Recently they became an AI code review tool, and just added a bunch of AI tools to the review UI, but you could just ignore it and the core functionality was still great.

▲

jacobegold 3 days ago | parent | prev | next [-]

stacked prs will only get better from here :) we have an incredible amount of resources to keep improving that part of our product.

▲

3 days ago | parent | prev | next [-]

[deleted]

▲

qudat 3 days ago | parent | prev [-]

check out a range-diff approach using patchsets: https://pr.pico.sh