🚀 The first day of launch week is finally here! 🚀 Starting the week off strong, today we're shipping the best way to collaborate on stacks of PRs. One of our most-requested features, engineers can now seamlessly collaborate on one another's stacks, right from the Graphite CLI. Read more and start collaborating on stacks today: https://gt.dev/collab

🚀 For the second day of Graphite launch week, we're excited to ship one of our most highly-requested features 👀👀 🔜 Starting soon, Graphite will automatically rebase your stacked PRs after you begin merging them — so you don’t have to. 🥞 Previously, if you wanted to merge the first 2 PRs in a stack of 4: you’d go to the 2nd PR on the Graphite dashboard, click “Merge 2 PRs,” and let Graphite handle the merging. 😭 However, you’d then end up in a state where the 2 remaining PRs in your stack would need to be rebased onto main. Previously, the easiest fix for this was to hop back over to your terminal and run

gt sync && gt submit

. 😫 This also led to inaccurate-looking code diffs on GitHub, as well as issues with codeowners and GitHub Actions workflows. ✅ To fix this, Graphite will start automatically rebasing your partially-merged stacks, so you don't need to! To learn more about how this change works under the hood, and to request early access, check out the blog post!

🎺🎺🎺 For day 3 of launch week, we’re excited to announce Graphite merge rules - designed to improve every team’s code review workflow, regardless of whether they've adopted stacking yet. As teams grow beyond a handful of engineers, it becomes increasingly important to codify how you determine if a pull request is ready to merge (i.e. have the right people approved it? has it passed the necessary CI checks?). Today, teams try to achieve this with a combination of

CODEOWNERS

(to assign reviewers) and branch protection rules, or by writing custom scripts and GitHub Actions workflows. But these fall short. Graphite merge rules is the next evolution of concepts like branch protection rules and codeowners, custom-built for fast-moving development teams. With merge rules, teams can customize & enforce their own codeowners and mergeability, define more granular merge requirements, and let authors override specific rules while still enforcing a high bar for quality. To see how Graphite customers are using merge rules and how it works under the hood, check out the blog post! 🚀

Teams use the Graphite merge queue to automate and speed up their merge process while keeping their trunk branches green 🟢 And most of these teams have been asking for the same thing, which we’re excited to announce today: batch merging 🧺 As you start using a merge queue, it’s important that it doesn’t slow down your releases or balloon your CI costs 💸 Batch merging is an effective strategy for both handling a higher volume of PRs while also reducing CI spend 📈📉 To learn more about how it works, check out the blog post 👉 https://graphite.dev/blog/merge-queue-batching

🚨 Tune in now for our live webinar with Graphite co-founder and CEO Merrill Lutsky! 📺 https://streamyard.com/watch/vyNVdjR6zGjk

To close out launch week, we’re excited to start solving one of the most painful problems every rapidly-scaling company faces: growing CI costs 📈💸 We've seen developers at fast-growing companies like Ramp and Asana become more productive because of stacking. But it's also common for organizations to see rising CI costs as their teams ship faster 🏎️ When you're shipping more, you're going to run CI more frequently—teams need to have a strategy in place to avoid ballooning costs and wait times 🎈⏰ Today we’re excited to announce first-class integrations with Buildkite and GitHub Actions that let you optimize your CI pipelines for stacking, so your releases stay reliable while your costs stay in control 😌😎 To learn more about optimizing your CI and how it works, 👉 check out the blog post! 👈

Tap in to ask @Greg and @Jacob Gold all your hard-hitting Graphite questions Live right now!!!🗣️📢 https://streamyard.com/watch/NkrBgK4iv3My

👋 We’ve noticed a handful of bugs reported recently related to the new collab changes and other misc. things. I wanted to acknowledge that we at Graphite are proactively working on fixing these and appreciate all the constant feedback! I recently released a new cli version to beta that addresses some of the issues and am continuing to monitor. 1.3.5 Beta release notes: https://graphite-community.slack.com/archives/C0604H4AM97/p1716412865757989 We’re hoping to move this version to stable in the next few days after some verification. If you’re interested in getting the fixes asap and helping test the newest versions of the cli, look into joining our beta group here https://graphite.dev/docs/beta-cli!

🤖✨ AI reviewer We're currently refining some AI-powered review features (for example, capable of automatically catching bugs on PRs). If you're interested, I'd love to chat about potential features, UX, or our plans for the beta rollout? Feel free to DM or email (tomas@graphite.dev) 🙂

X-posting to announce our new #C0761M0PJ4R channel! 🎬 Come take a look! 🎬 https://graphite-community.slack.com/archives/C0761M0PJ4R/p1717008378134509

✋ New GitHub app permissions A heads up: we requested new permissions for the Graphite app this morning! As a result, if you’re an admin for an org with the Graphite app installed, you may have received an email. What permissions changed? We now subscribe to a few new webhook events: • Merge queue entry added • Branch protection configuration changes • Repository ruleset changes These help us reflect changes you make to your branch protection rules and repository rulesets on GitHub in the Graphite UI and show whether your PR is merging via the GitHub merge queue. In addition, if there are outstanding Graphite app permissions requests for your org, GitHub includes those in this latest permissions request as well. As a result, you may also see the follow permissions requested from our previous update in December: • Deployments (read-only): to support rendering deployments in our PR page UI • Custom properties (read-only): to incorporate any GitHub repository rulesets in our calculation of whether a PR is ready to merge • Custom repository roles (read-only): to incorporate custom repository roles in our calculation of whether a PR is ready to merge • Workflows (read and write): to allow users to merge workflow file changes from Graphite What do I need to do? If you would like any of the functionality above, please accept the new set of permissions. Otherwise, feel free to ignore the permissions request; Graphite will continue functioning normally. ------ If you have any questions about any of the above, please don’t hesitate to ask!

🪵 We’ve added multitrunk support in the CLI! 🌲 🌴 🌳 🎄 You can now work on multiple trunks simultaneously without having to re-initialize Graphite to change trunks! Join the #C0604H4AM97 channel to get started using it now (more details here).

Coming to you from Graphite HQ, we’ve been listening to your feedback and are excited to share a whole bunch of new features and improvements available today! 1. 📊 LIVE this Thursday July 18: See data behind the trends in code review, engineering best practices, and AI 2. 💸 Reduce CI costs for Buildkite and GitHub Actions (public beta, read more!) 3. 🧺 Run CI on a batch of PRs all at once instead of one-by-one when merging (public beta, read more!) 4. 🪵 Multiple trunk branch support (public beta, read more!) 5. 📱Review code on mobile web 6. 🥞 Share stacks to Slack and Microsoft Teams

The State of Code Review 2024 is live! gopher party party parrot The findings are drawn from an analysis of ~6 million PRs that were merged on GitHub in the last year, and we look at things like merge speed, CI run time, and popularity of languages across different orgs. Merrill is hosting a webinar at 2pm ET today to talk about the findings and we'd love to see you there!!

🫵 You're invited! Come hang out with us in NYC Wednesday, August 21 at the gorgeous Hidden Lane Bar for a happy hour on us! Meet other Graphite users, persuade @Joyce Lu to prioritize your feature asks in person, and enjoy the end of summer with us! Spots are limited so grab your reservation then grab a mojito! 🍹 https://lu.ma/o9nrn6cb

Join us for an exciting conversation between Graphite CEO and co-founder Merrill Lutsky and Motion Head of Engineering Chander Ramesh as we talk engineering leadership, DevTools and migrating between GitHub and GitLab. Happening live now! https://streamyard.com/watch/JCiEBXvZT663

A lot of conversation today centers around using AI to write code. But what about reviewing code? AI can provide near-instantaneous feedback, allowing authors to address issues in real time without waiting for a human reviewer to become available. Check out our latest blog post to learn more.

🚀 Today is the day! 🚀 We are proud to announce Graphite Reviewer is officially live! Your high-signal AI code review companion, Graphite Reviewer delivers immediate, actionable feedback on your PRs. Building Graphite Reviewer wouldn't be possible without the support and feedback of our incredible beta users and the rest of the Graphite community. That means 🫵 <!here>! Show your support on our Product Hunt page and help us prove our users are the best. Thank you all again so much for stacking with us 🥞 ❤️ https://www.producthunt.com/posts/graphite-reviewer

We are going to be performing some database maintenance this Saturday (Oct 19) from 9:00 am EST - 10:00 am EST. We expect Graphite to be down for a few small windows during this time. We will provide update here once the maintenance is complete.

It's crossover time!! Graphite CTO @Greg will be joining Marcos Arribas (Statsig, Head of Engineering) for a friendly fireside chat on Thursday, November 14. This is your chance to hang out with Greg and Marcos and ask them all your hard-hitting questions about building devtools 😈 If you have more burning questions after the panel, find them at the reception and continue grilling them with food and drink in hand. Don't miss it! RSVP here: https://lu.ma/bjgav49c

◀️ Introducing

gt abort

and

gt undo

! 🔙 • ❌ Easily abort the current rebase operation and return to the state before the conflict was introduced • ✨ Magically undo the most recent Graphite mutation completely Feel free to start using the beta (instructions) and leave any feedback! https://graphite-community.slack.com/archives/C0604H4AM97/p1733863743117569

Happy holidays (code freeze time) from all your friends at Graphite! 🎄 https://graphite.dev/blog/code-freeze

Graphite's #YearInCode2024 is launching next week. See how you stack up against other engineers on our global leaderboard & reflect on your stats from the year including: • Number of commits • Number of pull requests • Number of reviews • Top coding languages and much more.

<!here> Graphite's Year in code 2024 is live! ✦ Look back on your 2024 coding journey with a personalized highlight reel and stats page. ✦ Visualize your contributions and see how you stack up against other devs around the world. Thank you all so much for an amazing year; Graphite wouldn't be where it is today without our community. Stay tuned for big things to come in 2025. 💜

<!here> wanted to drop in to personally apologize for the outages we’ve had this week - we know this isn’t up to the standard you expect from a core piece of developer tooling. We’ll follow up to share a full post-mortem shortly once we’ve had a chance to debrief. I’ve directed our team to focus entirely on stability for the next 2 weeks, and we’ll keep you updated as we ship improvements. We know we let you down this week, and we’re fully committed to building back trust in Graphite’s reliability in the coming months. 🙏

Hey folks! Wanted to share our postmortem for last week’s instability, which details what happened, how we addressed it in the short term, and what we’re doing to harden our systems and processes in order to ensure that it doesn’t happen again. We take stability very seriously at Graphite and understand that you have high expectations for tools that are central to your developer workflow. As part of our commitment to you, we’d like to be fully transparent about the mistakes that led to the incident and our learnings from the investigation and postmortem process. Our team has been fully focused on stability for the past week+ and we’ve already taken significant steps to improve our incident prevention, readiness, and response. That said, reliability will remain as one of our core focus areas in the coming weeks and months and I’m happy to chat more about what we’re doing and address any additional concerns that your team may have here. https://withgraphite.notion.site/External-Outage-on-Graphite-web-dashboard-and-CLI-1a12fae86070805bbad6f64c3a4de85f

Hey everyone! We are looking to let a few more teams off the Diamond (AI reviewer) custom rules waitlist. DM if you're interested 💎

Hey <!channel>, wanted to share two pieces of exciting news: First off, Graphite has just raised a $52 million Series B! This means that we'll be growing the team, have a lot more resources at our disposal, and will be accelerating our trajectory on building the best developer platform on the market. As part of this effort, and fueled by our new round of funding, we're also excited to announce that our AI reviewer is now a standalone product: Diamond. We're also introducing powerful new features to understand and augment your team’s code review process, including: • Customizable rules: Enforce your team’s unique coding patterns by importing your own style guide. • Comment settings: Enhance clarity by filtering out unwanted comments, ensuring a focused, high signal-low noise review experience. • Codebase awareness: Improve comment quality with context gathered directly from your codebase. • Review insights: Access analytics on comment metrics, including issue categories. • Suggested fixes: Accept code improvements with a single click. • Universal GitHub integration: Works in any repository, whether or not you have a Graphite plan. To learn more about both the raise, and the launch you can read the full blog post by Merrill. Thanks for stacking with us! We couldn't have hit these incredible milestones without our amazing users.

One of our most-asked-for features, Graphite now supports a direct integration with Linear: ✦ Unified issue tracking: See all associated Linear issues directly in the PR sidebar within Graphite. ✦ Efficient bug reporting: Link bugs directly to the proper PR. ✦ Seamless issue management: Create or link existing Linear issues from the PR page. Read more about the integration and how to get started in our launch post.

Announcing another Graphite integration: Graphite's stacking workflow is now natively supported in Tower 13! With Tower 13, you can now: • Create and manage stacked branches visually. • Restack branches with a click. • Track parent/child relationships across branches. • Submit PRs via Graphite. Read more about the integration in our release blog post and try it out today!