Skip to content

merge queue: checking #1967 on main (6309d0e) - #1972

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/702e56bb43
Closed

merge queue: checking #1967 on main (6309d0e)#1972
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/702e56bb43

Conversation

@mergify

@mergify mergify Bot commented Oct 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch concrete-bouillabaisse-w4am1x of the default queue, to test #1967 before it merges into main. Pushing to this branch or closing this pull request removes #1967 from the queue.

What this draft tests

Mergify checks that #1967 still passes CI on top of main. CI runs on this draft's code, built in this order:

  1. main at 6309d0e
  2. #1967, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

  • Mergify merges #1967 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 6309d0ea1b3d72f1f8614f6bb489415139556d6c
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1967
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
Required conditions to stay in the queue

Cuarroc and others added 4 commits October 27, 2026 22:20
@Cuarroc @codex
test(conversation): specify explicit sharpening controls
89521b6 
Test-First: src/components/ConversationView.sharpen.public.test.tsx::keeps sharpening named while waiting and never sends the rewritten draft automatically

Test-First: src/components/ConversationView.sharpen.public.test.tsx::keeps the waiting count and navigation and single cancellation of real questions

Test-First: src/components/ConversationView.sharpen.public.test.tsx::announces the final call after the actual open questions are answered

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
@Cuarroc @codex
feat(conversation): preserve named sharpening with Glass controls
0445aa1 
Keep phase feedback separate from the stable action and preserve the existing draft-only sharpening lifecycle.

Plan-ID: KR-04d-1-SHARPEN-CONTROLS

Test-First: src/components/ConversationView.sharpen.public.test.tsx::keeps sharpening named while waiting and never sends the rewritten draft automatically

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
@Cuarroc @codex
docs(plan): record the bounded sharpening controls delivery
f28cbef 
Plan-ID: KR-04d-1-SHARPEN-CONTROLS

No-Test: record the accepted provider facts delivery

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
@mergify @mergify-commit-signer
Merge of #1967
48d30f8
@mergify mergify Bot closed this Oct 27, 2026
@mergify mergify Bot mentioned this pull request Oct 27, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/702e56bb43 branch October 27, 2026 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Cuarroc