Release Story StudioGitHub to launch kitExplore the flow
Step 1

Connect GitHub without giving up control.

Release Story Studio starts with a read-only GitHub App. Invited workspaces can connect a repository; everyone else can inspect the example release first.

GitHub connection

Read-only repository access

The app requests the smallest practical read permissions so the studio can inspect pull requests, commits, tags, releases, labels, and linked issues. Release and tag reads come through repository contents access. Nothing gets published from this step.

Choose repositoryContinue with the example releaseGitHub opens the installation target picker before repository access is granted.
Import readiness

megacity-agency/release-story-studio is ready for read-only release import.

1 live repositories available. Last checked 2026-05-30T02:05:08.000Z.
Import selected release
Readymegacity-agency/release-story-studioRead-only import
Read-only inputs

What the studio needs from GitHub

  1. Repository metadata: readUsed as source evidence for the release kit.
  2. Pull requests: readUsed as source evidence for the release kit.
  3. Issues: readUsed as source evidence for the release kit.
  4. Contents, commits, tags, and releases: readUsed as source evidence for the release kit.
Connection design

The live connection is built around consent.

Invited teams install the GitHub App, choose the installation target, select which repositories are available, and review imported evidence before generation starts. Publishing stays separate from import.

InstallChoose repositories
ImportReview evidence
GenerateCreate the launch kit