Skip to content

feat: redesign merge box integration as native sub-row#355

Open
jd wants to merge 1 commit intomainfrom
devs/jd/feat/merge-box-redesign/Iffc8b73eadf4229d9521a2c142dd898d6781a794
Open

feat: redesign merge box integration as native sub-row#355
jd wants to merge 1 commit intomainfrom
devs/jd/feat/merge-box-redesign/Iffc8b73eadf4229d9521a2c142dd898d6781a794

Conversation

@jd
Copy link
Copy Markdown
Member

@jd jd commented Apr 13, 2026

Redesign the Mergify Chrome extension's PR merge box section from a
standalone block into a compact sub-row that blends with GitHub's
native UI.

Changes

  • Replace standalone Mergify section with an integrated row inside
    the merge box (logo + label + inline links + buttons)
  • Queue/Dequeue button toggles based on Mergify Merge Queue check
    run status (fetched from /checks tab on load, live-updated from
    expanded checks list)
  • Hide all action buttons on merged/closed PRs
  • Show fun randomized message when PR was merged by Mergify
  • Match GitHub's native button sizing (14px, 32px height)
  • Support both old (.merge-pr) and new (data-testid="mergebox-partial")
    GitHub merge box layouts

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

Copilot AI review requested due to automatic review settings April 13, 2026 13:49
@mergify mergify bot had a problem deploying to Mergify Merge Protections April 13, 2026 13:49 Failure
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 13, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 Required Reviews

Waiting for:

  • #approved-reviews-by >= 2
This rule is failing.
  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 🔎 Reviews

Wonderful, this rule succeeded.
  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

Wonderful, this rule succeeded.
  • body ~= (?ms:.{48,})

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR redesigns the Mergify Chrome extension’s GitHub PR merge box integration to appear as a compact, native-looking sub-row within GitHub’s merge box UI, including queue state detection and merged-by-Mergify messaging.

Changes:

  • Replaces the standalone injected “Mergify” merge section with a single inline row inside the merge box (logo, links, action buttons).
  • Adds queue state detection (DOM-based + initial /checks fetch) to toggle Queue/Dequeue and updates it on subsequent renders.
  • Adds merged-by-Mergify detection and displays a deterministic “fun” merged message on non-open PRs.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 9 comments.

File Description
src/mergify.js Reworks injection UI to a merge-box sub-row; adds queue state fetching/DOM detection, merged-by-Mergify detection, and new button rendering.
src/__tests__/mergify.test.js Adds unit tests for queue detection, merged-by-Mergify detection, and merged message selection.
docs/superpowers/specs/2026-04-13-mergebox-redesign-design.md Documents the intended merge box sub-row design and behavior.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@jd jd marked this pull request as ready for review April 13, 2026 13:53
@jd jd force-pushed the devs/jd/feat/merge-box-redesign/Iffc8b73eadf4229d9521a2c142dd898d6781a794 branch from 9df278a to f093ea7 Compare April 13, 2026 13:53
@mergify mergify bot requested a review from a team April 13, 2026 13:58
@mergify mergify bot had a problem deploying to Mergify Merge Protections April 13, 2026 13:58 Failure
@jd
Copy link
Copy Markdown
Member Author

jd commented Apr 13, 2026

New design:
CleanShot 2026-04-13 at 16 04 52@2x

@jd jd force-pushed the devs/jd/feat/merge-box-redesign/Iffc8b73eadf4229d9521a2c142dd898d6781a794 branch from f093ea7 to b0ea74a Compare April 13, 2026 14:11
@mergify mergify bot had a problem deploying to Mergify Merge Protections April 13, 2026 14:12 Failure
@jd jd force-pushed the devs/jd/feat/merge-box-redesign/Iffc8b73eadf4229d9521a2c142dd898d6781a794 branch from b0ea74a to ba00be3 Compare April 13, 2026 14:21
@mergify mergify bot had a problem deploying to Mergify Merge Protections April 13, 2026 14:21 Failure
Redesign the Mergify Chrome extension's PR merge box section from a
standalone block into a compact sub-row that blends with GitHub's
native UI.

## Changes

- Replace standalone Mergify section with an integrated row inside
  the merge box (logo + label + inline links + buttons)
- Queue/Dequeue button toggles based on Mergify Merge Queue check
  run status (fetched from /checks tab on load, live-updated from
  expanded checks list)
- Hide all action buttons on merged/closed PRs
- Show fun randomized message when PR was merged by Mergify
- Match GitHub's native button sizing (14px, 32px height)
- Support both old (.merge-pr) and new (data-testid="mergebox-partial")
  GitHub merge box layouts

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Change-Id: Iffc8b73eadf4229d9521a2c142dd898d6781a794
@jd jd force-pushed the devs/jd/feat/merge-box-redesign/Iffc8b73eadf4229d9521a2c142dd898d6781a794 branch from ba00be3 to 012163a Compare April 13, 2026 14:26
@mergify mergify bot had a problem deploying to Mergify Merge Protections April 13, 2026 14:26 Failure
Copy link
Copy Markdown
Contributor

@remyduthu remyduthu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants