Sounds quite right.

Makes me think of a related issue though, which is how to manage the "branching rules" for a repo (branch name conventions, regexes...) if repo set up is per user. So these options should be set at the repo level per team, and one repo can only be set up for a team. Or maybe for now we can have in ployst core multiple instances that ultimately point to the same git repo.