~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.13.0 Latest 2 packages, 1 image

1
10

Issues come before pulls in a repository's tabs and its card

Merged
Merged chadtmiller.com asked to merge into main from chadtmiller.com/knotless:web/issues-before-pulls

What changes

A repository's tabs read Code, Commits, Issues, Pulls: issues now come before pulls. Its social card shows its counts in the same order, open issues then open pulls.

Why

Asked for by the owner: issues first, in the tabs and the cards alike.

How it was checked

just look repository --element nav.tabs --all: the tabs in the new order on desktop and phone, light and dark, the phone's row scrolling as before. The card's order is the order of one array, which no test pins. Every page under a repository's tabs moves.

Shots-moved: all

🤖 Generated with Claude Code

Approved

This swaps the Issues and Pulls tabs in RepoHeader.svelte, and swaps the order of the two counts on the social card in card.rs. The tab is defined in one place, so nothing else needs the same change. No docs or change file are needed, since this touches neither the client nor crates/knotless/src. The body has a Shots-moved: all line, as the shots check requires. I didn't run anything: the check, test, web and shots checks were still queued or running when I looked, so wait for them to pass. The card's for loop lays the counts out "from the right edge leftward", so the first array entry is the rightmost. Putting pulls first therefore shows issues on the left and pulls on the right, which matches the tabs.

Merged as fa4f93f