Pull request thread, merge box

Pull request thread, merge box is a Activity Feed block from Orvain UI, built for React and Vue with a matching Figma frame.

Best for

Code review that ends in a merge: the checks run, then the button wakes

Anatomy

Rail of events · a checks ring and rows that run · a split Merge button with squash, rebase and merge · Undo on the toast

MCPConnect the MCP server
Add command-menu keyboard navigationacme/app #128 · Ava wants to merge 2 commits into mainOpen
Ava Rios opened this pull request Thu 17:20
Ava Rios· 10:02

Ready for review. Checks are running.

Mia Kwan approved these changes Approved 10:52
0 of 2 checks passedRunning · started 10:41
BuildQueued
Unit testsQueued
Waiting for checks
Enter sends, Shift and Enter adds a line.
Comment on #1280 / 280

In the Orvain Library

Get Pull request thread, merge box for your product

The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.

  • React
  • Vue
  • Figma frame
  • Orvain MCP

About this block

Part of Activity Feed

What’s inside

04parts

The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.

  1. Rail of events
  2. A checks ring and rowsthat run
  3. A split Merge buttonwith squash, rebase and merge
  4. Undo on the toast

Responsive behaviour

767 px

Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.

1440pxDesktop · 12 columns

When to use it

Where Activity Feed earns its place

Reach for Activity Feed

  • A record whose history mixes system events with what people said
  • Code review, where commits, a diff and check results belong to one thread
  • Team channels that need one place at the foot to answer from
  • Threads where the reply count matters more than every reply

Reach for something else

  • Alerts a person triages and clears: a notifications inbox with read state fits better
  • Dated milestones with no conversation around them: a timeline is lighter
  • Logs people filter, sort and export: give them a table

Accessibility

06to keep

What the block ships with. Hold on to these as you make it yours.

  • Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
  • Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
  • More than colourA state never rides on colour alone; a mark or a word goes with it.
  • Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
  • Calm motionFor visitors who ask for reduced motion, things simply appear.
  • Room to hitTargets stay at least 24px, with space between neighbours.

Notes for AI

1 line

Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.

Add the Orvain “Pull request thread, merge box” block to this page: rail of events, a checks ring and rows that run, a split Merge button with squash, rebase and merge, Undo on the toast.

Works in
Connect the MCP

Questions about Pull request thread, merge box.

What is the Pull request thread, merge box block?

Pull request thread, merge box is a Activity Feed block from Orvain UI, built for React and Vue with a matching Figma frame. Best for code review that ends in a merge: the checks run, then the button wakes.

What is the Pull request thread, merge box block made of?

Is the Pull request thread, merge box block responsive?

Is the Pull request thread, merge box block accessible?

How do I add the Pull request thread, merge box block to my project?

When should I not use a Activity Feed block?

More Activity Feed blocks

All Activity Feed

Thread feed

Team channels and project threads: a day of activity with one place to answer it

Thread feed, open in place

Busy threads where the replies should stay beside the message

Thread feed, catch up

Returning to a channel: what you missed, and where it starts

Pull request thread

Code review: commits, a diff and the checks that gate the merge

Pull request thread, inline review

Code review on the lines: comments live under the code they are about

Event rows

The rows a system writes: something happened, nobody said anything

Message rows

The row a person writes: what they said, who reacted to it and what you can do with it, in a live channel

Quoted entry

Anything an integration posts: a message pulled in from another surface

Event rows, stacks

Busy threads: a burst of changes folded into one line

Event rows, rail

The quietest feed: a timeline you glance down

Quoted entry, pull quote

A quote worth keeping: the message is the entry

Quoted entry, context

Quotes you want to check against the conversation around them

Message rows, quick react

A busy channel where one tap is the whole reply

Message rows, calm

A channel that is mostly reactions: the thread stays readable

Thread entries

Threads that carry something: an upload, under the replies it drew

Thread entries, by file

Threads about uploads: filter the replies by the file they are about

Thread entries, moments

Feedback on a capture or a document: replies pinned to a second or a page

The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.