Repo-first onboarding, Watching & Release Risk Assessments
New workspaces walk a repo-first setup — GitHub, repositories, production branches — and land on a project home that watches those branches.
Repo-first onboarding
Create a workspace and you are in a guided path: name it, connect GitHub, pick repositories, map production (and any extra environments), then review. Nothing else turns on — rollouts, Control points, and observability stay later. Teammates who are not owners wait until an admin finishes, instead of bouncing through a flow they cannot complete.
Watching on the project home
Once repositories are bound, environments mapped, and change release analysis is on, the project overview leads with Watching — which branches are covered and the latest reading — instead of a setup checklist. New project no longer opens the old walkthrough.
Release Risk Assessments
A Release Risk Assessments tab lists every pull-request run into a watched branch. The advisory comment stays on the GitHub pull request; the console is the record. Change release analysis is a per-project opt-in on the AI Release Engineer tab (off by default) and needs a one-time acknowledgement that repository code may be sent to a model provider.
Improved
- The GitHub repository picker is grouped by account, and can offer to rename the workspace to match the organisation
- Every branch of a repository is listed before the project exists, so production mapping is a choice, not a guess
Fixed
- Onboarding card copy stays readable on the char face