Skip to content

merge queue: checking #1894 on main (60aa6ac) - #1895

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/01d39e391a
Closed

merge queue: checking #1894 on main (60aa6ac)#1895
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/01d39e391a

Conversation

@mergify

@mergify mergify Bot commented Oct 25, 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 senior-rillettes-dbuiz7 of the default queue, to test #1894 before it merges into main. Pushing to this branch or closing this pull request removes #1894 from the queue.

What this draft tests

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

  1. main at 60aa6ac
  2. #1894, 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 #1894 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 60aa6ac17afb89cc5f88e220db1f9bf7dbb7d7fb
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1894
    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 25, 2026 01:51
@Cuarroc @codex
test: cover project chat drafts across route lifetimes
117bdc9 
Exercise the real route composer through the mocked Tauri boundary. The regression fails when returning to the route loses the first draft.

Plan-ID: KR-04b
Test-First: src/shell/mount/verlauf.mount.test.tsx::retains project drafts across routes and settles only the submitted revision
Co-Authored-By: GPT-6 Astra <noreply@openai.com>
@Cuarroc @codex
test: cover first-send completion after route return
b15d956 
Require genuine history after an in-flight first send completes across navigation. Also observe the empty-state claim at the history read boundary.

Plan-ID: KR-04b
Test-First: src/shell/mount/verlauf.mount.test.tsx::loads the accepted first conversation after returning during its send
Co-Authored-By: GPT-6 Astra <noreply@openai.com>
@Cuarroc @codex
fix: retain project chat drafts across route navigation
babf5f9 
Keep one current draft and its pending send/error per project in UI-session memory. Clear only the acknowledged text revision and discover a first conversation when a send completes after route return. Reuse the existing history reader and preserve classic callers.

Plan-ID: KR-04b
Test-First: src/shell/mount/verlauf.mount.test.tsx::retains project drafts across routes and settles only the submitted revision
Test-First: src/shell/mount/verlauf.mount.test.tsx::loads the accepted first conversation after returning during its send
Co-Authored-By: GPT-6 Astra <noreply@openai.com>
@mergify @mergify-commit-signer
Merge of #1894
af81a3b
@mergify mergify Bot closed this Oct 25, 2026
@mergify mergify Bot mentioned this pull request Oct 25, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/01d39e391a branch October 25, 2026 00:38
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