It seems like it's going to be tricky to balance between flexibility to support all kinds of workflows and streamlined experience by standardizing workflows. Where does Runway stand in terms of this tradeoff?
But in general - it is tricky, and I think the perfect balance changes depending on what type of a team we're talking about. We've talked to small teams, larger ones with more complex structures (like multiple product teams all contributing code to a single binary), but also teams who are fairly agnostic about their branching and tooling setup, and those who are more opinionated.
There is certainly a version of Runway that could be much more prescriptive (and limited) for teams who prefer more guidance in setting up a release toolchain. For now, we're trying to hit a sweet spot of enough flexibility to meet the needs of most teams, while encouraging best practice in a few areas that we think will streamline everyone's process.
It's an ongoing conversation and it's really helpful to hear from individual teams on how Runway could help in their specific situation.