Skip to content

codeSplitters: make the mirror sync box simple and visual #693

Closed

Description

@QuinnsCode

Owner, testing mirrors in the desktop app (#609, #407): "that UI flow could be easier, clearer, simpler, visual." Today the mirror box in the repo sidebar is a paragraph: a tag (`in step`, `rewritten`, `clash`), the upstream URL, a Sync now button, then sentences about commit identity, clashes and where git truth lives. After a force-push it explains itself in prose, and you have to read it to choose between Re-base on upstream and Take upstream's.

Make it something you take in at a glance:

  • A small picture of the two sides: GitHub ↔ here, each with its latest commit (short sha, message, time), and an arrow or icon for the state: in sync ✓, ahead ↑n, behind ↓n, diverged, rewritten.
  • State in one word with an obvious icon; neutral or calm for "in sync". Today `in step` uses the orange-outline tag, which reads like a warning (same problem as Following, codeSplitters UI polish: running list from the #609 click-through #678).
  • Choices as two cards that show their result, not their mechanism: "Keep my 2 commits, put them on top of GitHub's" vs "Match GitHub exactly (drops my 2 commits)", each listing the commits it keeps or drops. Only show them when there's a choice to make.
  • Sync now as an icon button with the last-checked time beside it.
  • Move the fine print (commit identity, "Where git truth lives") behind an ⓘ.

Keep labels on one line (owner's taste: obvious icons over wrapping words).

🤖 Generated with Claude Code

Activity

  1. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Owner, after both force-push rounds passed: "I think we can massively make git simpler with visuals of what each is doing technically." So go wider than the mirror box: every git action on the site (sync, re-base, take upstream's, merge a branch, push the crew's copy) shows a small before → after picture of the commits on each side, so you see what it does before you press it.

  2. self-assigned this
    on Oct 11, 2026
  3. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Owner, while trying to start a branch (#609): "how do i branch it in the ui … some of this should just be real visible and easy like whatever git options you need". Today Start a branch and Merge a branch exist only in the ⌘K palette (client.html:3679), and editing on a branch means adding ?branch=<name> to the URL by hand (the toast says so). So, as part of this:

    • a visible branch switcher on the repo and file pages (main ▾, with your branches, "+ New branch", and upstream's for a mirror), the way GitHub and VS Code have one
    • once you're on a branch, every edit goes there, with a clear "on branch X" marker and Merge / Push to upstream buttons right there
    • the same before → after picture for each of these actions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions