Repository navigation
merge queue: checking #782 on main (7a7a2bd), stacked on 4 pull requests ahead - #797
Closed
mergify[bot] wants to merge 16 commits into
Closed
mergify[bot] wants to merge 16 commits into
mergify[bot] wants to merge 16 commits into
Conversation
Test-First: src-tauri/src/questions.rs::questions::tests::store_fixture_drop_waits_for_connection_return_and_directory_removal
Extract the existing predicate unchanged and reproduce the KI-25 remainder with a compiling regression test. Test-First: src-tauri/src/setupgate.rs::process_state_classification_rejects_zombies_and_dead_states
Hand off the Tokio worker while joining cleanup so SQLx connection-return tasks can finish. Drop TempDir outside the runtime context to keep Windows cleanup retries synchronous, and assert removal without polling. Test-First: src-tauri/src/questions.rs::questions::tests::store_fixture_drop_waits_for_connection_return_and_directory_removal
Test-First: scripts/lib/dev-mrp-count.test.mjs::countRp recognizes all current Mergify package branches Test-First: scripts/lib/dev-bench-weekly.test.mjs::weekly package counts follow current Mergify prefixes and preserve package IDs
Match the sibling testgate helper so dead processes cannot appear alive during setup cleanup assertions. Test-First: src-tauri/src/setupgate.rs::process_state_classification_rejects_zombies_and_dead_states
Test-First: scripts/lib/dev-mrp-count.test.mjs::countRp recognizes all current Mergify package branches Test-First: scripts/lib/dev-bench-weekly.test.mjs::weekly package counts follow current Mergify prefixes and preserve package IDs
The full prepush suite exposed one connection remaining after SQLx close completed. Re-drain the closed pool until empty before removing the directory; preserve the strict pool-size assertion and avoid timed polling. Test-First: src-tauri/src/questions.rs::questions::tests::store_fixture_drop_waits_for_connection_return_and_directory_removal
No-Test: documentation only (acceptance matrix reconcile)
No-Test: documentation-only KI-25 status update; regression covered by the preceding commits.
Test-First: scripts/lib/dev-push-verified.test.mjs::PUSH-REMOTE: option-like remote refuses before push
Test-First: scripts/lib/dev-push-verified.test.mjs::PUSH-REMOTE: option-like remote refuses before push
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎉 This pull request has been checked successfully and will be merged soon. 🎉
#782 is queued for merge on branch main (7a7a2bd).
Stacked behind 4 pull requests queued ahead of this batch, not part of it. These checks run on a tip that also carries their commits, so a failure here can come from them as much as from #782.
Queued ahead of this batch:
This pull request has been created by Mergify to speculatively check the mergeability of #782.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue rule
defaultfor merge:check-success = gates (linux)check-success = gates (windows)check-success = red-firstgithub-review-approved[🛡 GitHub repository ruleset rulemain-pr-required-checks]label != do-not-mergemain-pr-required-checks]:check-success = @github-actions/gates (linux)check-neutral = @github-actions/gates (linux)check-skipped = @github-actions/gates (linux)main-pr-required-checks]:check-success = @github-actions/gates (windows)check-neutral = @github-actions/gates (windows)check-skipped = @github-actions/gates (windows)main-pr-required-checks]:check-success = @github-actions/red-firstcheck-neutral = @github-actions/red-firstcheck-skipped = @github-actions/red-firstmain-pr-required-checks]:check-neutral = @mergify/Mergify Merge Protectionscheck-skipped = @mergify/Mergify Merge Protectionscheck-success = @mergify/Mergify Merge ProtectionsRequired conditions to stay in the queue:
-conflict-draftbase = maincheck-success = gates (linux)check-success = gates (windows)check-success = red-firstgithub-review-approved[🛡 GitHub repository ruleset rulemain-pr-required-checks]label != do-not-mergelabel = review-okmain-pr-required-checks]:check-success = @github-actions/gates (linux)check-neutral = @github-actions/gates (linux)check-skipped = @github-actions/gates (linux)main-pr-required-checks]:check-success = @github-actions/gates (windows)check-neutral = @github-actions/gates (windows)check-skipped = @github-actions/gates (windows)main-pr-required-checks]:check-success = @github-actions/red-firstcheck-neutral = @github-actions/red-firstcheck-skipped = @github-actions/red-firstmain-pr-required-checks]:check-neutral = @mergify/Mergify Merge Protectionscheck-skipped = @mergify/Mergify Merge Protectionscheck-success = @mergify/Mergify Merge Protections