惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
博客园 - 司徒正美
C
Check Point Blog
G
Google Developers Blog
The GitHub Blog
The GitHub Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
有赞技术团队
有赞技术团队
P
Proofpoint News Feed
IT之家
IT之家
B
Blog
博客园_首页
量子位
MongoDB | Blog
MongoDB | Blog
博客园 - Franky
J
Java Code Geeks
H
Help Net Security
A
About on SuperTechFans
Apple Machine Learning Research
Apple Machine Learning Research
Jina AI
Jina AI
D
DataBreaches.Net
Y
Y Combinator Blog
大猫的无限游戏
大猫的无限游戏
云风的 BLOG
云风的 BLOG
Google DeepMind News
Google DeepMind News

Graphite blog

Introducing Code Tours: a new way to review Introducing Cursor Cloud Agents in Graphite Building the future of software development with Cursor Reimagining the PR Page: Designing for speed and focus Graphite changelog [11-20-2025] Graphite changelog [11-04-2025] Graphite changelog [10-16-2025] The future of engineering is collaborative (and already here) Meet Graphite Agent: the next evolution of AI code review Introducing frozen branches: A safer way to build on your teammates’ work Graphite changelog [09-17-2025] How we sped up code search for Graphite Chat Introducing Graphite Chat AI is writing code—here's why it also needs to review that code How I got Claude to write code I could actually ship How we built the first stack-aware merge queue (and why it matters) How we organize our monorepo to ship fast Graphite brings stacking to Tower Code review tooling: Should you build or buy? Making AI code review available to everyone Introducing: The new Graphite + Linear integration Graphite raises $52M and launches Diamond to reimagine code review for the age of AI Why AI will never replace human code review How stacked PRs unblock distributed development teams Graphite is going to Developer Week 2025 Beating the end of year code freeze How Graphite’s eng team ships code remarkably fast Why we chose Anthropic's Claude to power Graphite Reviewer AI code generation will remain fragmented How we redesigned Graphite's landing page in-house
Multiple engineers can now seamlessly collaborate on the ...
Stephen Pink · 2024-05-06 · via Graphite blog

Since the earliest days of Graphite, we’ve heard from users that they want to collaborate on the same stack of PRs with their teammates in real-time. Stacking your own PRs is challenging enough without a tool like Graphite, so it’s no surprise that managing a collaborative stack of PRs from multiple authors is next-to-impossible with vanilla Git. We started shipping the foundations for collaborative stacks all the way back in v0.19 of the Graphite CLI, and since then we’ve iterated and refined the experience based on all the great feedback from users in our collaboration beta.

Today, we’re excited to announce that all developers using Graphite can now confidently work together with their teammates on a shared stack of PRs - simply gt get, gt create, and gt submit to fetch and share changes.

Why collaborate on stacked pull requests?

Stacking your own changes is a powerful way to stay unblocked, organize your work into logical pieces, and get faster, higher-quality feedback in code review. Collaborative stacks take this to the next level - now you can build on top of a teammate’s work without blocking them from merging in their changes today.

You can even use a shared stack to divide up work on a feature across your team - so one of you can write the data model changes, another can build the backend logic, someone else can add the API endpoints, and you can get started on the front-end all at the same time.

Create your first shared stack

You can easily create shared stacks with the Graphite commands you already know and use every day:

  1. Fetch a teammate’s PR with gt get. You can copy the full command from the pull request Graphite pull request page by clicking on the branch name.

  2. Then, run gt create to create a new branch on top of the one you fetched.

  3. Lastly, run gt submit to create a stacked pull request on top of your teammate’s PR.

Here’s what a shared stack looks like in Graphite - it’s just like a normal stack, but with PRs from different authors.

If your teammate pushes changes to the PR you’ve stacked on top of, the CLI will prompt you to pull in their changes with gt sync.

How Graphite collaboration works under the hood

Behind the scenes, Graphite automatically resolves and reconciles the complex Git states needed to make collaboration possible. Think about the last time you ran git pull --rebase and had to resolve rebase conflicts for each of your local commits. When Graphite detects you've made local changes more recently than remote changes, it will automatically rebase your local state on top of the incoming remote changes — so you don’t have to.

Getting started

To start collaborating on stacks, update your CLI to v1.3.4+ (full changelog).


After hearing so many of you ask for a better experience for collaborating on stacked pull requests, we’re so excited to release full support for shared stacks. We started Graphite to give teams Git superpowers, and we can’t wait to see what you build with them.

Related articles