Skip to content

merge queue: checking main (cc0c6ba) and #1765 together - #1768

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/269cce6b9e
Closed

merge queue: checking main (cc0c6ba) and #1765 together#1768
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/269cce6b9e

Conversation

@mergify

@mergify mergify Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (cc0c6ba) and #1765 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #1765.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: cc0c6ba1379819b1083c8c1450a8b82f2e485d0e
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1765
    scopes: []
scopes: []
...

jd and others added 2 commits August 7, 2026 18:04
`colors_enabled()` opened with `if cfg!(test) { return false }`, whose
comment claims tests "never depend on the dev's TTY". It cannot do
that: `cfg!(test)` is false whenever mergify-tui is compiled as a
dependency, so the guard only ever covered mergify-tui's own tests.
Every *consumer* crate's tests fell through to the real policy and read
the developer's environment — `FORCE_COLOR=1 cargo test -p
mergify-events` fails on main today, on escape sequences injected into
asserted output.

Gate on the recorded `--color` choice instead. `set_color_choice()` is
called from exactly one place, `detect_dispatch()` in main, so an unset
choice means the process did not come through the CLI: a test harness,
a doctest, an embedder. Colors stay off there, in any environment,
across every crate.

`resolve_enabled()` takes the `Option<ColorChoice>` so the new case is
covered by the existing precedence unit test rather than by global
state.

Refs MRGFY-8533.

Change-Id: Id7eb12b906409122000a14722e5ce172ab93cb4c
@mergify
mergify Bot deployed to Mergify Merge Protections August 10, 2026 12:24 Active
@mergify
mergify Bot temporarily deployed to func-tests-live August 10, 2026 12:24 Inactive
@mergify mergify Bot closed this Aug 10, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/269cce6b9e branch August 10, 2026 12:30
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.

1 participant