Checking connection

CODE REUSE, RECONSIDERED

Good code.
New ground.

The feature you need already exists.
Give it a home in your codebase.

Explore workspace See the method

TWO REPOSITORIES. ONE INTENTION.

FIG. 01 / THE TRANSPLANTILLUSTRATION
A feature, not a forkTwo wireframe repositories. A small group of implementation, test and helper files moves between them while the surrounding code stays put. 01 / SOURCE02 / DESTINATIONMOVE THE FEATURE
TAKE WHAT MATTERS.
LEAVE THE REST IN PLACE.R—01
FEATURE, NOT FORK.TESTS TRAVEL WITH IT.YOUR REVIEW. YOUR REPO.

01 / THE METHOD

Less rebuilding.
More building.

Describe the behavior you want to keep.
Review how it fits somewhere new.

01

Point to two repositories.

Where the feature lives. Where you want it next. Your destination stays yours.

02

Name what should travel.

Repot traces the implementation and related tests, then prepares an adapted draft.

03

Make the final call.

Inspect the changes and the gaps. Download a patch or publish an authorized draft PR.

02 / NOT JUST THE CODE

Bring the behavior.
Keep the evidence.

Related tests belong with the feature.
Not in the repository it left behind.

ILLUSTRATIVE JS/TS MAPPING · NOT A RUN RESULT

TRANSFER ANATOMY
SOURCEsrc/csv.tsDESTINATIONlib/export/csv.ts

Adapt the implementation to its new surroundings.

SAME INTENTION DIFFERENT ADDRESS

03 / THE WORKSPACE

A new home.
On your terms.

CONNECTING

Start with your GitHub account.

The connected beta is invite-only. Explore the workspace below; repository actions require sign-in.

Checking connection
New feature transfer

New transfer

01 — SPECIFY
Describe the behavior. Include what must stay unchanged.0 / 1500
SIGN IN TO PREPARE A TRANSFER
02 — REVIEWNO TRANSFER SELECTED

Every change, considered.

Choose a saved transfer to inspect its files, related tests, and proposed changes.

Your next feature starts with a clear intention.
YOUR ACTIVITY

Saved transfers

Sign in to see your transfers. No repository data is stored in this browser.

Data & access 24H DRAFT RETENTION

On the connected service, selected code and access tokens are encrypted in the database. Drafts expire after 24 hours. Deleting your Repot data does not delete GitHub pull requests or provider-side data. Minimal usage counters remain for up to two UTC calendar days to prevent quota resets.

THE NEXT CHAPTER OF YOUR CODE

Don’t start over.
Start from something.

Find it a new home