Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Pull Request Merged Success Block for React

A confirmation panel for a merged pull request: a commit graph drawn in SVG beside the same history as a list, a group of buttons that dims one lane, the twelve checks as one count, the deploy in three timed steps and the merge hash with a copy button.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Show where a merge landed with this confirmation panel for React with Base UI. It is the panel Diffhaven, a code-review tool, shows once a pull request is merged: a header with one action, the Shine Button that opens the repository, over one framed card ruled by Guides. The first cell is the history as a graph: six commits, newest first, each a row with its lane drawn beside it in SVG (main as filled dots, the branch as hollow ones, the merge commit joining them, the branch's end dashed because it was deleted), and a Toggle Group that dims the commits of the other lane. The second cell holds the twelve checks as one count and three lines, the deploy in three timed steps and the merge commit's hash with a Copy Button. For code hosts, review tools and any change that ships on merge.

FAQ

What stays in the page, and how do I wire it for real?

Nothing was merged or deployed. The six commits, their hashes, the twelve checks and the deploy times are typed sample data, and the lane buttons only change which commits look dimmed. The merge hash is copied through the browser's clipboard. To wire it, fill COMMITS newest first from your history (each with its lane and its parents' ids), GROUPS from the pull request's checks and STEPS from the deploy's events; the graph's lines and dots are worked out from the commits and their parents.

Is the graph accessible?

The drawing is hidden from assistive technology and the list beside it is its text equivalent: each commit is a row with its subject, short hash, the author's initials and the day, and the rows that matter carry a note (the merge commit, the deleted branch, where the branch started). A caption read only by screen readers says how the lanes join. The graph is left-to-right whatever the page's direction.

What do the lane buttons do?

They are a group of three buttons (All, main and the branch) with one always on. Choosing a lane dims the other lane's commits and lines, keeps every row in place so the panel never changes height, and says how many commits are still lit.

How is the graph drawn, and how do I change the history?

Each row is 64 pixels tall and the graph is one SVG of the same height with two vertical lanes. Every edge is worked out from a commit and one of its parents: a straight line within a lane, a curve between lanes, so adding a commit to COMMITS moves the dots and lines with it. The end of a deleted branch is a dashed stub and a cross drawn from its newest commit.

What does the copy button copy?

The full 40-character merge commit hash, a typed sample, while the panel shows its first seven characters. A screen reader hears that it was copied.

  • Pro

    Deployment Live Success

    Builds and deploys

    A confirmation window for a live deploy: a drawn browser with the real address and a copy button, a group of buttons that redraws the site at desktop, tablet and phone width, and the deploy's facts and four passed checks beside it.

  • Pro

    Build Passed Success

    Builds and deploys

    A confirmation window for a green build: a bar of four stages as wide as their share of the run, a typed terminal log for the chosen stage with a once-only replay, a small artifacts table and a local Deploy this build.

  • Pro

    Schema Migrated Success

    Builds and deploys

    A confirmation panel for three database migrations: figures worked out from the ledger, an accordion of the migrations with their SQL as plus and minus lines, and a Roll back button that asks in an alert dialog before it changes the ledger.

  • Pro

    Project Created Success

    Account lifecycle

    A confirmation page for a new project: the repository as three facts and a themed code box with bun, pnpm, npm and yarn tabs, each with the same four lines and a button that copies the open tab, over one Open the dashboard button.

  • Pro

    Integration Added Success

    Integrations and syncs

    A confirmation panel for a new Slack connection: the first alert drawn as a greyscale message that a channel menu redraws, the two marks, the workspace and scopes, a local test message and one Open settings button.

  • Pro

    API Key Show Once Success

    Security and access

    A key confirmation inside an app panel: the secret masked with an eye toggle and a real copy button, a checkbox that turns it into its stored form, the key's scopes and dates, a request that uses it, and a Done button that waits for the box.