Team pipeline profile and layered preferences
The idea
Onboarding proposes how the team works (design first, test first, trunk, approvals, strict paths, stage shares), with a backtest over 30 merged PRs. Accepted settings resolve in layers, with the person's own layer on top.
- The problem
- One fixed pipeline does not fit every team, and defaults overrode what people chose.
- Why it matters
- The runtime follows the team's accepted process, and the person's own way wins.
- Where it stands
- In production as of
A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.