Change

log

The Pierre Documentation has been completely overhauled with an all new design and dozens of new pages to showcase and explain our features, workflows, integrations, and more. Whether you’re brand new to Pierre, joining an existing workspace, or just curious from the sidelines, there’s plenty to learn about in the docs.

Some of the highlights include:

• Multiple new getting started guides for folks brand new to Pierre or joining a team
• New feature and workflow guides for Workspaces (formerly known as Teams), Branches, Reviews, and Drafts
• New FAQs and keyboard shortcuts pages
• Updated integration guides
• ...and more!

The all new design comes with beautifully generated page banners, a new sidebar navigation, an improved responsive design, and typographic improvements for our MDX-based content, media, and code snippets.

As you explore the new Pierre Docs, don’t forget to jump into our Discord with any feedback or suggestions.

We've built an all-new GitHub app to mirror your repositories hosted on Pierre back to GitHub. This is a great way to keep your repositories in sync across multiple origins as you get to know Pierre, but also helps teams that need to work in private and in public.

Mirrored changes currently only go from Pierre to GitHub, so it's best to avoid pushing any changes directly to that repository on GitHub. Mirrored repositories push (not force push) all changes to all branches in a given repository. We recommend setting Pierre as your new origin remote (and renaming your GitHub one to upstream) to avoid accidental pushes.

Once setup, all you need to do is git push {origin} {branchName} and your push will first go to Pierre and then to GitHub.

For more information, read our GitHub + Pierre docs page.

We're sprinkling a little magic on branches starting this week with AI-powered summarization and categorization of your code changes. All branches, open and merged, will now stream in a high level summary alongside a list of 2-5 of the most notable changes in the branch. All with zero configuration or setup.

The above screenshot is an example from a recent branch that added our new docs pages. It sounds wild, but in practice, these have gotten good enough already that our own commit messages and branch descriptions are essentially redundant.

These categories now help convey the type and intent of changes in a branch. It's never been easier to understand if a branch contains UX changes, data layer changes, API changes, dependency changes, etc.

This also means diffs are no longer strictly alphabetical. With one click, you can quickly filter or sort by the tags on any branch. Reviewers can now get to the changes they care about most instantly. We can't wait to see review times drop and the quality of feedback improve with these summaries.

More AI-powered features are on the way, so stay tuned! Jump into the Discord to get early access and share any feedback.

We know product teams work together at all stages of the product lifecycle, so we've updated our powerful rich-text editor to include multiplayer support! Now anyone with Editor access to your branch can collaborate with you in real-time on a single, shared canvas.

From the Share modal, invite teammates to your branch and give them Editor access to enable multiplayer editing.

Have any feedback or feature requests? Let us know by joining our community Discord.

Starting this week users on Pierre can now @-mention their teammates in posts and comments. This is a great way to get someone's attention when you want them to see something without explicitly asking for a review. Along with that comes a new bell icon at the top of the sidebar that notifies you anytime you're mentioned.

You know the drill—type @ and a menu of your teammates will appear. Use your arrow keys or mouse to select a team member. Results automatically filter as you type.

What would diffs look like if they were optimized for comprehension? Could we convey more by showing less? Could we leverage dynamic UI conventions and AI to let you dig deeper, but only when you needed? How could we help quantify review time and give you the tools to improve it?

Our answer? Blended diffs.

Blended diffs reimagine how versioned code changes are shown to reviewers by minimizing deleted lines, simplifying modified lines, and providing more context around a set of changes. All while improving the review process and making it more approachable for the whole team. Starting today, it’s the only diff style on Pierre.

By emphasizing a file’s after state over a decades-old diff design, we drastically reduce the level of visual noise while giving space for previously unseen levels of context around code changes. Okay, enough talk, let's walk through some of the changes!

Starting from the top, you'll see a new set of diff stats. We now show three numbers: additions, deletions, and modifications. What are modifications you ask?

Modifications are singlular changed lines. They replace the old deleted and added lines of yesteryear and are indicated with a blue ~ character and striped border (shoutout VS Code!). Inline additions are highlighted with a green background while inline deletions are indicated by a vertical red bar. Click that red bar to open a popover that shows the before and after for that line.

Blended diffs also include a dedicated column left of the line number called a gutter. The gutter is where we show additional relevant information for code changes. This is where annotation markers are now rendered, avatars for authors that left a comment on that line, and more.

Finally, deleted lines are now hidden by default and their changes are summarized by AI. Deletions can be shown by clicking the summary text or subtle red horizontal line.

Blended diffs are a massive leap for code review on Pierre. In the future we'll be adding more functionality to blended diffs, including expanding diffs to show more of the file, commenting on files, reference files, suggested changes, and more.

Happy branching! Jump into the Discord for early access and to tell us what you think.

The Pierre Changelog is here to keep you up to date on all the latest changes to Pierre. Stay in the loop as we ship new features, address bug reports, and improve Pierre with your feedback. Have any feedback or feature requests? Let us know by joining our community Discord.

Images now show up in diffs! Image files that are newly added will simply be rendered on their own while modified images are rendered in as a side-by-side comparison.

Pierre was built to be realtime from the very beginning. We already show you who's online and actively viewing branches, plus who's viewed it recently.

Now we've built a new status sidebar to show you who's online and, if they're reviewing something, the name of the branch that they're working on. Meet someone where they're working, or see if it's a good time to ask them a question.

More connected teams ship better code, and better products.

The Pierre CLI now automatically detects Prettier, Typescript, ESLint, and Vercel! One command generates a branch for each one so you can review, merge, and get back to what matters most. Run npx pierre@latest from any repo to get started.

If you can believe it, our file explorer just got even better. We now render Markdown (and give you an option to flip to the source) inline when clicking a .md file in the tree. Similarly, we now render SVGs inline with an option to flip to their HTML source code. We also render common binary images inline.

Pierre’s logged out homepage has a new look, and a whole new story to tell. Say hello to Pierre, the product engineering tool. One place for product engineers and their teams to focus on building their products.

Starting today, Pierre generates an estimated time to review on every branch with suggestions for how authors can reduce code review time. Time to Review (TTR) estimates are based on total lines changed, code complexity, and other heuristics.

In the future, we’d love to add additional insights like authors’ familiarity with code, how often/recent the code has been changed, etc.

We’ve shipped a massive mobile update to make Pierre much easier to use on your phones and narrow viewports. Your recent branches and reviews should be much easier to navigate to, and branches also now much faster to use with easy access to things like our share sheet and branch activity view.

Get on the Pierre hype train with our the new Pierre CLI! Once you’re signed up for Pierre, jump to terminal and run npx pierre@latest to get started. Our CLI will authenticate you, setup your SSH, find or clone the right repository, and connect you with your team.

Read the Pierre CLI docs for details on supported commands.

There’s a new side to Pierre with our snazzy, snappy new file explorer. We kept finding ourselves wanting to pull up a repo’s file tree for quick comparisons and references. Access from the context menu of any repo in the sidebar. Hit t to quickly file search. Shared URLs auto-expand the tree to highlight the current file.

We’ve redesigned Pierre with a brand new team-focused sidebar navigation. It’s now easier than ever to switch or create new teams, but more importantly, everything you need is so much more accessible now. Setup folders to group related repos, quickly create new ones, access search, and jump to your recently pushed branches or review requests.

Watch the video below for a quick tour of the new sidebar.

There’s a new integration in town—Pierre now connects with Discord! There are two components to our Discord integration—one for teams, one for individuals.

To get started, head to your team’s settings and connect Discord. This will broadcast Pierre activity like new branches, comments, merges, approvals, and more to your Discord server members.

From there, each workspace member can head to their user settings to connect their Discord and Pierre accounts so we can use your Discord username to @-mention you with new activity.

Continuous integration for Pierre has arrived, and boy is it a doozy. We’ve reimagined what CI could look like for today’s software teams.

1. Jobs are written in Typescript, not YAML.
2. Using our CI SDK, you can create and update custom gauges on branches to visual stuff like Lighthouse scores, bundle size, preview builds, etc.
3. You can create inline (or page-level) annotations to directly highlight things like type or lint failures.

Of course all the good stuff is still there, too—a list of jobs, quick access to logs, and a commit/log explorer.

Read the Pierre CI documentation to learn more.

We’ve built a custom Linear integration just for teams on Pierre. Connect Linear with your team to enable rich issue embeds in branch descriptions and update issue status when branches are merged or archived.

Head to your team settings page to connect Linear.

Pierre helps teams set clearer context earlier in a product's development by bringing the team—engineering, product, and design—together in one place. To help, we’ve added third party embed support to our editor. Drop in links to Figma files, Linear issues, tweets, YouTube videos, and more to see them in action.

Hey there! We're a team of developers who helped build GitHub, Coinbase, Medium, Twitter, and more. Now we're building Pierre to reimagine industry-old primitives with a new developer platform for teams that build and ship software.