Mergifyio / Mergifyio/browser-extension

Feature Request: Add a Dequeue Button

Open
#468 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
4
Forks
2
Avg merge
11m
Merged PRs (30d)
79

Description

Summary

It would be great to have a dequeue button directly in the Mergify browser extension. This would allow users to remove a pull request from the merge queue without having to leave the browser or interact with the Mergify dashboard or API manually.

Motivation

Currently, if you want to dequeue a PR, you need to either:

  • Use the Mergify dashboard
  • Post a comment with a Mergify command
  • Use the Mergify API

Having a dequeue button in the extension would make this much more convenient and keep the workflow entirely within the GitHub UI.

Proposed Solution

Add a "Dequeue" button alongside the existing queue-related actions in the extension. Ideally it would appear on the PR page when the PR is currently in a merge queue, and clicking it would trigger the dequeue action via the Mergify API.

Additional Context

This would be a nice quality-of-life improvement, especially for teams that frequently need to reprioritize or remove PRs from the queue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the extension's existing queue-related actions and its Mergify API integration. Verify how PR-page actions determine queue membership and how the dequeue request is triggered. Done means a Dequeue button appears for queued PRs and removes the PR through the API without using the dashboard, comments, or manual API calls.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, html
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.