Change feeds
Change feeds
A live, newest-first page of screenshots for one repo — or one pull request.
What a feed is #
A feed is a live public page of screenshots already tagged with a GitHub repo. With a feed you can:
- Share the latest shots for a repo behind one
/c/<id>URL. - Scope that same feed to one pull request or issue.
- Open one shot at
/c/<id>/<item>and page through the set. - Filter by page path (the same
pathmetadatauploads finduses).
It is the same product either way — one extra filter. New tagged screenshots appear automatically. A gallery is a curated set you add by hand.
Anyone who knows the URL can view the feed. GitHub repository visibility does not restrict it.
Create a feed #
Create a repo-wide feed. This prints its public URL. Omit --repo and the CLI uses the current git
remote:
uploads feed create --repo owner/repoCreating the same scope again returns the existing URL.
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 feed to one page path.
Open an existing feed with uploads feed show.
From a hosted agent (no local CLI), call MCP feed_create with repo, plus
pr when the feed should stay on one pull request. github alone can
supply both. feed_get returns the current shots and the public URL.
Page through the set #
Each shot has its own page at /c/<id>/<item> — previous / next, and a 1 of N count. The feed
list links into that pager. Older /feed/… links redirect there.
Syncing the managed PR comment creates the PR-scoped feed if it does not exist yet (the same
idempotent create as uploads feed create --repo … --pr …). Each image in that comment then links
to its feed item page. The <img> still loads from the embed URL.
Standalone /f/… pages stay for one-off shares. Curated galleries are unchanged.
Gallery, repo, or PR #
- Gallery — you pick and order the files. See Galleries.
- Repo feed — the latest screenshots across a repo.
- PR feed — the same feed, scoped to one pull request.