Live links
Get started
GitHub
Live links
A live, newest-first page of files for one repo, or one pull request.
What a live link is #
A live link is a public page of the files already tagged with a GitHub repo. With a live link you can:
- Share the latest files for a repo behind one
/c/<id>URL. - Scope the same link to one pull request or issue.
- Open one file at
/c/<id>/<item>and page through the set. - Filter by page path (the same
pathmetadatauploads finduses).
A live link updates on its own: new tagged files appear without anyone adding them. To hand-pick and order a set instead, use a gallery. See Live link or gallery.
Anyone who knows the URL can view the live link. GitHub repository visibility does not restrict it.
The CLI, API, and MCP call a live link a feed. uploads feed create,
MCP feed_create, and the /feeds REST routes all create or read one, and
its URL starts with /c/.
Create a live link #
Create a repo-wide live link. This prints its public URL. Pass owner/repo or --repo. Omit both
and the CLI uses the current git remote:
uploads feed create owner/repouploads feed create --repo owner/repoCreating the same scope again returns the existing URL. A workspace holds up to 50 repo-wide live links. Pull request and issue live links have no cap.
Want only one pull request? Add –pr, or pass –github with
owner/repo#123 or a GitHub URL. –issue does the same for an issue.
Optional –path keeps the link to one page path.
Open an existing live link with uploads feed show.
From a hosted agent (no local CLI), call MCP feed_create with repo, plus
pr when the link should stay on one pull request. github alone can
supply both. feed_get returns the current files and the public URL.
The PR comment #
Syncing the managed PR comment creates the pull request’s live link if it does not exist yet. The
comment then opens with a line like 12 files · View all on uploads.sh → that links to it.
Each file tagged with that pull request links to its own page in the live link. A file whose
gh.* metadata names a different pull request keeps its /f/ link. The <img> still loads from
the embed URL.
The comment posted through your local gh (no GitHub App on the repo) shows the same line and
links. Turn both off with linkToFilePage: false in .uploads.yml.
Page through the set #
The live link page shows 50 files at a time, newest first. Older files opens the next page.
Each file has its own page at /c/<id>/<item>, with newer and older links and a 1 of N count. Older
/feed/… links redirect to /c/….
Standalone /f/… pages stay for one-off shares.
Live link or gallery #
Use a live link when you want to follow what changes. Use a gallery when you want to choose what people see.
| Live link | Gallery | |
|---|---|---|
| What’s in it | Every file tagged with the repo, or one PR or issue | Only the files you add |
| Order | Newest first | The order you choose |
| Upkeep | None. New files appear on their own. | Add each file with --gallery |
| Use it for | Following a repo or PR as it changes | A release, demo, or review set |
A repo live link and a PR live link are the same thing with one extra filter.