Design system

Open changes across repos

See one design change across its pull requests in several repos: each lane's state, its stories and the merge order.

Last updated November 15, 2026View as Markdown

In the pilot

The design system module is in the pilot: it is on for pilot orgs first. An org admin can tell you whether your org has it.

A design change often spans several repos: the spec, the React library, the Vue library. The Open changes page shows each change as one card, with one lane per pull request. The page only shows: you merge, tag and re-pin on GitHub as you do today.

The page needs the design module on your org and a design system with at least one repo source. Every member with a role on the system opens it; what each lane shows depends on the repos you can read on GitHub (below).

Open the page

Open the design system and choose the Open changes tab. It lists the open pull requests to the default branch of each repo source, plus those merged or closed in the last 7 days that belong to a change still open. Pull requests that were open before the system was registered appear too.

If the page is empty, it says which repos it follows. With no repo source, it reads "Add a repo source to follow its pull requests" (see The design system record).

How lanes join into one change

EasyCode joins pull requests from different repos into one change on the strongest signal it finds:

  1. Pin: a library pull request pins a commit of another open pull request, such as the spec's.
  2. Branch: the same branch name in two repos.
  3. Link: one pull request's description names the other.
  4. Task: both link the same EasyCode task, a design request included.

Each card lists its evidence, one line per join, for example "React #40 pins spec #12's head". The spec lane comes first. Two pull requests in the same repo never join.

Read a lane's state

Each lane shows one state:

StateMeaning
Checks passingEvery check passed
Checks runningA check is still queued or running
No checksNo check ran on the head
Failing: namesOne or more checks failed
Waiting for the spec tagIts only failures are checks that wait for a spec release
ConflictsThe pull request cannot merge as it is
MergedMerged
Closed without mergingClosed
Checks could not be readGitHub did not answer

Beside the state you may see Draft, No reviewer requested or Checking for conflicts.

A library lane that pins a spec commit with no release yet is noted "Pinned to an unreleased spec commit; re-pin after the tag". A library source can name the checks that fail until the spec is tagged; when only those fail, the lane reads "Waiting for the spec tag" instead of failing.

See what changed

Each lane lists, with no build:

  • Components added, changed and removed.
  • Tokens changed, with their old and new values, and a swatch for a colour.
  • Stories by path: the story files the pull request changed.
  • Stories: the stories added and removed, when the system has a hosted Storybook for that library and the pull request has a preview. Otherwise it says "Stories compared by path only" or "Stories: not hosted".

A new design file is read only after it merges.

Open the preview

EasyCode does not build your pull request. It finds the preview your CI published: a deployment, a check run's details link, a source's preview address rule, or a bot's comment. A preview opens only from a host an admin approved in Settings → Design. While EasyCode looks, the lane reads "Looking for the preview…"; after about 38 minutes without one, "No preview found for this commit".

  • Open preview opens it in a new tab; each added story opens at its own path.
  • Review on GitHub opens the pull request.
  • Review opens the review on live frames: see Review on live frames.

Desktop app only

Open in the browser pane lists your live sessions, those on the lane's repo first, and opens the preview in the chosen session's pane. There you can pick an element and send it to the session's agent. With no live session, it asks you to start a session on the repo first.

Follow the merge order

When a change holds a spec lane and a library lane that pins it, the card shows the Merge order. Each step is done, next or waiting:

Tag a spec release

Done when a release of the spec holds the merge. If EasyCode cannot tell, it says "Can't tell which tag holds this merge".

Merge the libraries

Each step links its pull requests on GitHub. After a merge, the lane reads "In the unreleased view" once the record has caught up, or "Merged, the record follows within" the source's lag until then.

Join or split a lane

When EasyCode groups lanes wrongly, fix it from the lane's menu. A contributor or maintainer of the system, or an admin, who can read both repos on GitHub can:

  • Move a lane to another change (choose the change).
  • Make its own change, splitting it out.
  • Undo to remove the override and let the signals decide again.

What you see without access to every repo

Lane details come from code, so they follow GitHub. A lane in a repo you cannot read shows only its role, such as "React library: 1 lane in a repo you cannot read on GitHub". A change made only of such lanes is counted at the end of the page, not shown, and evidence naming a hidden lane is dropped.

Next

Something wrong or missing? Suggest a change

On this page