Help
Watching a repo
What SuperPost reads from GitHub, how often, and what a new release does.
Paste a public repository URL and SuperPost reads the README, the file tree, package metadata and the latest releases. For a private repository, install the SuperPost GitHub App from Connections; it asks for read access only, and reads use your installation, never a stored password. With the GitHub App installed, GitHub tells SuperPost the moment you publish a release or merge a change. A public repository without the app is checked on a schedule instead. A release becomes one draft on the Queue for approval; smaller changes are gathered into a weekly digest. SuperPost does not post anything on its own. If you would rather trigger it from CI, the release Action in Connections → GitHub App → Release Action uses a token made for your product. It only tells SuperPost a release happened; it does not post to any network. The Product Brain is rebuilt when you press Rebuild on the Brain screen. Claims whose file changed are marked stale until they are checked again. What is read from a repository stays in your workspace. The ledger on the Brain screen shows every claim with the file and lines it came from; edit or strike a claim and the change is kept across rebuilds. The public changelog at /c/owner/repo is only hosted for a repository GitHub confirms is installed on your account.