Publish check

Before you publish

Updated 1 Nov 2026 · 2 min read

Build › Publish check helps you check that you haven't made something public by accident. It lists only what changed since you last marked a publish. Mind can't tell whether code works or is safe: it lists what changed, what the features make public and what GitHub reports; the rest is yours to confirm.

Your first check looks back 30 days, and never before the day the new MindBacklog came on for your workspace: it says Since the new MindBacklog came on with the date. Features you completed before then are not shipped by your first Mark as published; they reach your map through Build › Map's review of shipped features.

What it shows

  • What changed: commits and merged pull requests that reached your default branch (when GitHub is connected), stories and bugs that moved, documents set Final, and features shipped. What coding agents said they built is listed apart: it's their account, and the commits are the evidence.
  • What it makes public: for each feature that changed, what its Build Pack says it makes public (a page, a route, data, an AI endpoint or a file, who can open it, a rate limit). It comes from the spec, never from your code; items Mind drafted are marked until someone confirms them.
  • The checks:
    • Checked by data: the GitHub checks on your latest commit, and open secret-scanning alerts. When GitHub reported nothing, the result is Unknown, never a pass.
    • You confirm: each public item is what you meant, the Build Pack's checklist for those features, and "Nothing else became public". Confirm each one, or skip it with a reason.

Mark as published

When every check is confirmed or skipped with a reason, Mark as published (editors) records every check and its result, with an optional note, and starts the next check from now. It never blocks you. If a commit named a story that isn't Done, it offers to mark it done as a plan you can apply. The history on the right lists every publish you marked.

Without GitHub the check works from your stories and documents; connect GitHub (a repository webhook: no code access) in Settings › Connections to see commits and checks.