Live streamJoin us for "State of code review 2024" on July 18thRegister today
Background gradient

After this full week of launches, we want to share our upcoming roadmap with you, our incredible community!

We fundamentally believe software engineering can be better. Developers should be able to spend more time building and obsessing over users, and less time fighting their tools, doing manual work, and reviewing code.

So to make that a reality, what’s next for Graphite?

Imagine this scenario: you’ve been building a new search feature and submit a stack of pull requests for your team to review.

Your coworker asks you to rename the API endpoint for your feature — a change that affects both the web frontend, mobile app, and backend of the feature. The code change is trivial but you’d spend more time checking out each individual branch or manually amending each individual commit than it would take to make the change itself.

This is where gt absorb comes in. “Absorb” (born at Facebook for Mercurial), automatically identifies which commits to add your staged changes to and amends them — leaving you with more time and clean git history.

👉 Sign up to get notified when gt absorb is available.

We’ve loved hearing about all the automations you’re building to auto-assign reviewers, add labels, and leave helpful comments on PRs.

Going a step further, we want to take the pain out of CI for developers. We’re going to let you start, stop, skip, or restart CI with Graphite automations. This means you’ll be able to automatically re-run that flaky test or skip irrelevant tests to save on CI time.

You’ll also be able to trigger automations based on failed CI checks. Automatically leave comments with links to runbooks & wikis, apply labels, or tag teammates in response to CI events.

👉 Sign up to get notified about Graphite automations for CI!

Going another step further, we’re going to let you trigger automations on code patterns in pull requests. This means you’ll be able to automatically…

  1. Notify the PR author when they use a deprecated code pattern or API

  2. Keep designers in the loop when a PR touches human-readable strings

  3. Keep the security team informed when dependencies change

👉 Sign up to get notified when automations supports code patterns!

Time is of the essence when it comes to merging your PRs, and we're going to make it faster. If you’ve ever gone to merge a PR and either:

  1. Needed to re-run CI and resolve merge conflicts several times before finally merging

  2. Broken the build because someone else merged a conflicting PR at the same time

… then you probably need a merge queue.

The Graphite merge queue helps main stay green and frees you up being glued to watching CI to make sure your merge succeeded.

And we’re making it even faster with Parallel CI.

Parallel CI uses a technique called speculative execution, a term coined by Uber engineering, which runs CI on many branches in parallel and then merges them in first-in-first-out order. It has an added benefit of a green lineage on main, meaning it’s safe to revert to any point in its history.

👉 Sign up to get notified when Parallel CI is available!

We’re adding new Graphite insights to make it easier to understand how well you’re doing when it comes to shipping smaller PRs.

👉 Sign up to get notified about new Graphite insights!

We’ve been hard at work making the Graphite web app faster and easier to navigate, so you can always find the pull request or page you’re looking for. This is available today.

It’s important to know if a tool actually made your life better.

At Graphite, we spend a lot of time researching code review. In fact we routinely spend hours looking at the data on what makes productive developers able to ship so much code. We read the academic research of others, but we also conduct our own. Now that more people than ever are engaging in code review, we're taking this opportunity to dig into the data. Some of the questions we’ll be looking at are:

  • How do different teams approach code review?

  • How do engineers engage with this step of of the development cycle, and what can be done to make it better?

  • What assumptions should we (the developer community) be challenging?

We're hoping to explore these questions and more in our State of Code Review report later this year, drawing from nearly 8 million pull requests across more than 100,000 engineers. Coming soon this spring! Stay tuned.

Graphite Q1 launch week is now complete! Thank you so much for joining us as we got to talk about all of our exciting launches. In case you missed it, re-play our launch week webinar on-demand by our co-founder & CEO Merrill Lutsky.

Jan 16: Accelerating code review

Jan 17: Making stacking seamless

Jan 18: Stacking with the tools you love

Jan 19: What’s next for Graphite + live webinar (today)

Give your PR workflow
an upgrade today

Stack easier | Ship smaller | Review quicker

Or install our CLI.
Product Screenshot 1
Product Screenshot 2