Does it work with private repositories?

Yes. The connection is authorised in GitHub with your account and reads only the repository and paths you select.

Does Scripe read source code?

It reads the paths you choose. Most teams pick docs, changelogs and READMEs; code is only read if you point at it.

What if we disconnect?

The connection is removed and the documents that came from it are deleted from the knowledge base.

Integration

Release notes and READMEs become posts.

Connect a repository and Scripe reads what shipped, so product updates reach LinkedIn while they are still news.

GitHubScripe

What shipped, read from the repository.

For teams whose product lives in code, the truest source is the repository.

Knowledge base

Release notesSynced
CHANGELOG.mdSynced
README.mdSynced

Choose the paths, Scripe reads the files.

Connect a repository and pick the paths that matter: docs, changelogs, READMEs. Scripe reads them into the knowledge base and keeps them current with the tree.

Release notes become drafts.

A new release note in the repository is a source for ideas: the product lead's post about what shipped, in their own voice. By default a draft is created; what gets published is what you approve.

Evidence

Outlier · Lea Brandt, 6.4× her average

Knowledge base · the 14 Sep call, Granola

Positioning · marketing leads, 11-50-person B2B

Every claim points at the file.

When a draft draws on the repository, the card names the file and quotes the passage, so the engineer approving it sees the source.

What the repository gives you.

What Scripe reads from a repository, and what it deliberately leaves alone.

All integrations

Paths, not everything
Only the paths you choose are read; code stays code.
Current with the tree
A changed file updates its document; a removed file removes it.
For product teams
Founders and product leads post what shipped while it is still news.