Skip to content

Show CI progress below the notch by default - #101

Merged
jordan-cod merged 2 commits into
mainfrom
feat/live-ci-style
Nov 18, 2026
Merged

jordan-cod merged 2 commits into
mainfrom
feat/live-ci-style

Conversation

@jordan-cod

Copy link
Copy Markdown
Owner

Why

The live CI wings sat beside the notch, over the menu bar icons next to it. With a crowded menu bar they hid two or three icons. On macOS 27 the menu bar is a single window, so Pullo can't find those icons (without Accessibility access and a private framework) to make room for them. Other notch apps don't detect them either. Boring Notch, for example, lets you choose between showing things below the notch and beside it.

What

  • A new LiveCIPlacement setting: Below the notch (default) or Beside the notch (the old layout), in Settings › Appearance with previews.
  • Below the notch, the closed notch keeps its width and grows 24 pt down, showing the ring, the label and the +N count. If the label doesn't fit a narrow notch (the 120 pt tab on Macs without a notch), it widens as needed.
  • NotchLayout takes the LiveCI itself and asks it for the closed size, so the hit area follows either layout.
  • Strings in pt-BR and es. The Appearance footer no longer says the notch "widens".
  • Tests: the default and persistence, the closed size in both layouts, and a narrow notch.

Before

After

(The selected sidebar row renders black in offscreen captures, in both versions.)

🤖 Generated with Claude Code

The live CI wings sat beside the notch, on top of the menu bar icons
next to it. On macOS 27 the menu bar is a single window, so Pullo cannot
see where those icons are and make room for them.

CI progress now hangs below the notch by default, which leaves the menu
bar alone. Settings > Appearance can put it back beside the notch.
@jordan-cod
jordan-cod merged commit 1f9acee into main Nov 18, 2026
3 checks passed
@jordan-cod
jordan-cod deleted the feat/live-ci-style branch November 18, 2026 01:50
@jordan-cod jordan-cod mentioned this pull request Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant