Skip to content

docs: move Browser Extensions out of the Merge Queue section#11825

Merged
mergify[bot] merged 1 commit into
mainfrom
devs/jd/worktree-update-stacks/move-browser-extensions-merge-queue-section--2e6ed322
Jun 16, 2026
Merged

docs: move Browser Extensions out of the Merge Queue section#11825
mergify[bot] merged 1 commit into
mainfrom
devs/jd/worktree-update-stacks/move-browser-extensions-merge-queue-section--2e6ed322

Conversation

@jd

@jd jd commented Jun 12, 2026

Copy link
Copy Markdown
Member

The browser extension now surfaces Stacks context (the stack chain and
revision-history timeline) in addition to merge queue controls, so
nesting it under Merge Queue no longer fits.

Relocate the page to /browser-extensions and group it with the CLI under
a new top-level Tools nav group, move its images alongside it, broaden
the content with a Stacks panel section, repoint the inbound links from
the stacks docs, and add a 301 redirect from the old URL.

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

Depends-On: #11822

@mergify mergify Bot had a problem deploying to Mergify Merge Protections June 12, 2026 15:53 Failure
@jd

jd commented Jun 12, 2026

Copy link
Copy Markdown
Member Author

This pull request is part of a Mergify stack:

# Pull Request Link
1 docs(stacks): sync stacks docs with current CLI #11820
2 docs(stacks): add "vs Plain Git" comparison page #11822
3 docs: move Browser Extensions out of the Merge Queue section #11825 👈
4 refactor(stacks): extract shared install snippets into partials #11826
5 docs: install the CLI via the install script #11839

@mergify

mergify Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

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

🟢 ⛓️ Depends-On Requirements

Wonderful, this rule succeeded.

Requirement based on the presence of Depends-On in the body of the pull request

🟢 🤖 Continuous Integration

Wonderful, this rule succeeded.
  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • check-success=Cloudflare Pages
      • -head-repo-full-name~=^Mergifyio/

🟢 👀 Review Requirements

Wonderful, this rule succeeded.
  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = mergify-ci-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|ui)(?:\(.+\))?:

🟢 🔎 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,})

@mergify mergify Bot requested a review from a team June 12, 2026 15:55
The browser extension now surfaces Stacks context (the stack chain and
revision-history timeline) in addition to merge queue controls, so
nesting it under Merge Queue no longer fits.

Relocate the page to /browser-extensions and group it with the CLI under
a new top-level Tools nav group, move its images alongside it, broaden
the content with a Stacks panel section, repoint the inbound links from
the stacks docs, and add a 301 redirect from the old URL.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I2e6ed322d24c29e7e1ed4e72f456b9461784952d
@jd jd force-pushed the devs/jd/worktree-update-stacks/move-browser-extensions-merge-queue-section--2e6ed322 branch from e6f6714 to c042289 Compare June 13, 2026 19:26
@jd jd force-pushed the devs/jd/worktree-update-stacks/add-vs-plain-git-comparison-page--7f58b122 branch from ce4c04e to 9cb8af6 Compare June 13, 2026 19:26
@jd

jd commented Jun 13, 2026

Copy link
Copy Markdown
Member Author

Revision history

# Type Changes Reason Date
1 initial e6f6714 2026-06-13 19:26 UTC
2 rebase e6f6714 → c042289 (rebase only) 2026-06-13 19:26 UTC

@mergify mergify Bot had a problem deploying to Mergify Merge Protections June 13, 2026 19:26 Failure
@jd jd marked this pull request as ready for review June 15, 2026 13:17
Base automatically changed from devs/jd/worktree-update-stacks/add-vs-plain-git-comparison-page--7f58b122 to main June 16, 2026 07:50
@mergify mergify Bot force-pushed the devs/jd/worktree-update-stacks/move-browser-extensions-merge-queue-section--2e6ed322 branch from c042289 to 3636e4d Compare June 16, 2026 07:51
@mergify mergify Bot deployed to Mergify Merge Protections June 16, 2026 07:51 Active
@mergify mergify Bot requested a review from a team June 16, 2026 07:53
@mergify

mergify Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Queued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 minutes 32 seconds in the queue, including 1 minute 59 seconds running CI.

Required conditions to merge

mergify Bot added a commit that referenced this pull request Jun 16, 2026
@mergify mergify Bot added the queued label Jun 16, 2026
@mergify mergify Bot merged commit 63e07c4 into main Jun 16, 2026
8 checks passed
@mergify mergify Bot deleted the devs/jd/worktree-update-stacks/move-browser-extensions-merge-queue-section--2e6ed322 branch June 16, 2026 08:22
@mergify mergify Bot removed the queued label Jun 16, 2026
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