Thank you! The button should be on the left side of the existing buttons so that when adding it, we don't move the existing one.

when logged out

Refined GitHub does not support "logged out". Any code related to it should be removed from this PR

Please don't force-push to this PR, it makes it harder to see what changed since the last review.

We merge commits rather than squash, so we care more about reviewability than a clean history. Feel free to push dirty commits.

Moved the button to the left side of the previous button

Hey @fregante I have reached the open PR limit since my previous PR (#10181) is not yet merged.

Two issues:

• the tip text is inheriting the title styles: it probably just needs one extra class like text-body or whatever GitHub already uses to reset the font style/size to it
• the button stays on non-Conversation tabs after visiting the Conversation: you can fix this by using the components/url.ts store inside the .svelte component and toggle the hidden attribute, e.g. <action-menu hidden={!pageDetect.isConversation(url)}>

Minor issue: the button still causes a shift of the "New issue" button on mobile, because the "New issue" button is now left-aligned. Same goes on the PRs and its buttons.

Desktop ✅

Mobile ⚠️

Solution

I'd only accept a solution to this if it's CSS-only. If not, good as-is for now.

Accepted places:

I'm still seeing it on the wrong side

Resolved the issue as below

1] Desktop view -

2] Mobile view -

Thank you for the screenshots! Can you also verify the PR one?

Yes its working correct there too

1] Desktop view -

2] Mobile view -

One last check I forgot is the sticky header in PR. Just "it works" is enough and I'll merge

One last check I forgot is the sticky header in PR. Just "it works" is enough and I'll merge

Yes that works too

Uhm, maybe you didn't push some commits? It's missing from me in the sticky header and it's on the left side of the buttons:

Uhm, maybe you didn't push some commits? It's missing from me in the sticky header and it's on the left side of the buttons:

Hi @fregante,

Thanks for catching that! I investigated the issues and resolved both:

1. Sticky Header: In the PR sticky header, the long branch byline had nested flex containers defaulting to min-width: auto and branch names up to 35vw, which forced the container to horizontally overflow on narrow viewports and pushed the right-aligned <action-menu> off-screen / behind side panels. I've added proper flex shrinking/truncation so the byline truncates cleanly with ellipsis and the filter button stays visible at the right edge with standard margin.
2. Button Ordering on Mobile: Observed [class*="menuActionsContainer"] across desktop, mobile context actions, and sticky headers, and applied CSS order rules to keep the primary buttons (New issue / Merge & Code) in their natural positions without shifting.

Since this PR was already merged, I've opened a follow-up PR with the fixes here: #10228 .

Can you explain where those screenshots came from? You said it works and posted the screenshots. Did you lie?

Can you explain where those screenshots came from? You said it works and posted the screenshots. Did you lie?

Why would I lie. Anyways the issue was of screen sizing. When viewed on complete desktop size screen for me it would show the sticky header. But while resizing the screen to reduce the width the button overflowed out of the window. This behavior was the reason you were unable to see the sticky header. Also same was the issue with the action button on the left side of the merge button in the pr view.

Can you explain where those screenshots came from? You said it works and posted the screenshots. Did you lie?

Why would I lie. Anyways the issue was of screen sizing. When viewed on complete desktop size screen for me it would show the sticky header. But while resizing the screen to reduce the width the button overflowed out of the window. This behavior was the reason you were unable to see the sticky header. Also same was the issue with the action button on the left side of the merge button in the pr view.

This might help you understand. Still facing the same issue.