Set a staging branch per repository

You can keep unfinished work separate from what you have actually shipped. If your team builds in one branch and delivers from another, tell featury which branch is staging for each repository.

When you set a staging branch, pushes and pull requests on that branch show as in construction. They only join your product map and changelog when they are promoted to the branch you monitor for delivery.

Set the staging branch

Add it when you connect or edit a repository. Branch fields suggest the real branch names, so you can pick without typing the exact name.

If you monitor a branch that is not the default, featury suggests the default branch as staging. That covers the common setup where main is for integration and prod is for delivery.

Tracking a staging branch costs no AI credits. See Pay for the AI you actually use.

What you will see

Work on the staging branch carries a staging badge in the change feed and overview, so you can tell at a glance what has not reached delivery yet. The promotion pull request from staging to your monitored branch appears only once.

Each release lane lists the work that was merged, with the date it landed. Select any entry to open its pull request, or its commit for direct pushes. The list shows up to 150 entries. If there are more, a link opens the full comparison on your code host.

For background, see See what is being built before it ships and See what each release delivered.