Skip to content

Tracker PR sub-row spends three lines on connector, title and base pill #15441

Closed

Description

@clubanderson

What

In the Activity Monitor (stage tracker), a PR nested under its issue (drawn with the ↳ connector) stacks its header on three lines above the chevron strip:

  1. the ↳ connector on its own line,
  2. 🤖 #15343 📖 docs: remove duplicate README run routes (author icon, number, title),
  3. the base-branch pill v5 on its own line,

then the chevrons. With a lineage chip (#15407) the title block wraps and the row grows further (124 px for a long title at 1400 px wide; 67 px for a short one).

Owner: "consolidate from 3 lines of text to 1 to compact the row".

Why

.ham-head-cols .ham-seg.ham-head-pr is flex-direction: column, so every child of the PR cell (connector glyph, PR link, base pill, lineage chip) is its own row, and .ham-pr-title / .ham-title are white-space: normal so long titles wrap.

Expected

One line: ↳ 🤖 #15343 📖 docs: remove duplicate README run routes · v5, then the strip. Long titles ellipsize on a single line (full title on hover); the lineage chip stays on the same line after the title and before the base pill, giving way before the title when space is tight; pills never shrink. The issue row and the top-level PR header keep to one line the same way.

Activity

  1. hivecommons-hive commented on Oct 29, 2026

    @hivecommons-hive
    Contributor

    🔒 Claimed by @mrbobbytables (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 29, 2026
  3. hivecommons-hive commented on Oct 29, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by @mrbobbytables released (lease revoked).

  4. github-actions commented on Oct 29, 2026

    @github-actions
    Contributor

    @clubanderson this issue was closed by @hivecommons-hive[bot] as completed.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions