File owners and editors: access control

If I have a file I want to control contributions to, I should be able to:

  1. Set some users as “owners” who can approve merge requests
  2. Set other users as “editors” who can open merge requests
  3. Leave still others as “viewers” who can do neither

Today, I have a library I need to keep maintained, but it’s terribly easy to accidentally make a change to a file if you have edit access, and not realize that you’ve left unpublished changes on that file.

In this world, editors could still freely open branches and explore (perhaps they’re considering adding a new design system component, or updating our text styles) without having to ask permission, but the main file is still kept tightly controlled and “clean.”