mooring

REPO

Switch repo

The copilot uses GitHub Copilot, which signs in separately from your GitHub login — it can even be a different account.

In the browser, enter this code at github.com/login/device:

NOTEBOOKS	STATE

No notebooks yet — click New notebook to create one, or Pull to fetch your team's notebooks.

GitHub accounts

Each repo syncs as one of these. Switching repos switches account, so you can't push under the wrong identity.

Add an account

git already has a credential for these hosts. Signing in this way needs no OAuth app, and mooring stores no copy of the credential.

Somewhere else? Add it by hand below — a host with no entry in your git config can still be borrowed once you name it.

Short name GitHub URL OAuth client id

The client id comes from an OAuth app registered on that host with Device Flow enabled. Ask your admin — or use instead, which needs no client id.

Connect a team repo

Connect to a team repo to sync and share your notebooks. Ask your admin for these values:

Owner Use an existing repo Repo Create a new repo

New repo name Private Add notebooks/ and data/ folders

Repo owner Repo name

Branch Short name (optional)

Connect to GitHub

Enter this code at your GitHub sign-in page:

Waiting for you to authorize…

Getting started

Scheduled refreshes

Refresh

Repeat On On At

Pull the team’s latest first (falls back to your copy if it can’t) Save an HTML snapshot to your local outbox each time

Notebook	Repeats	Status	Actions

Nothing scheduled yet. Pick a notebook, then in its panel’s SCHEDULE block choose “schedule refresh” (“verify & schedule” while it has not run clean yet) and mooring will pull, re-run and report on it on the cadence you choose — hourly, daily, weekdays, weekly, or once on a date.

A refresh never pushes; any snapshot stays in your local outbox.

Run for each value

Run

For

Save an HTML snapshot per value to your local outbox

Value	Status	Artifact / reason

Values run one at a time, and one failing value never stops the others. Nothing is pushed — artifacts stay in your local outbox.

Last operation

Create / view the pull request on GitHub

History

Read-only: old versions are never opened in the editor or run.

Version	Actions

Review changes

Merge cell by cell

Nothing is published — after merging, push the file like any other change.

What's new

File	Status	Changed

Workspace

Notebook packages

Health check

Checks your setup in plain English — network, login, config files, notebook packages. Nothing runs until you click.