Skip to content

PD 503 sub-repository permissions tracking: complete implementation

Created by: bobheadxi

This is a tracking issue for the complete implementation of PD 503: Sub-repository permissions model, formerly RFC 503. This follows our work on developing a proof-of-concept (milestone 139), and it primarily covered spikes on an implementation path and work that has carried forward on syncing permissions from Perforce (https://github.com/sourcegraph/sourcegraph/issues/26644) and the sub-repo perms smart client (https://github.com/sourcegraph/sourcegraph/issues/26645).

See the November 15 update for more details on the outcome of the proof-of-concept, and the complete implementation roadmap for an overview and discussion of the path forward.

Background

Some code hosts support permissions being set against more granular items than repositories, which is currently all Sourcegraph supports. The high level aim of this project is to add support for permissions at a more granular level than repo.

See PD 503 for a complete overview.

Tracked issues

@unassigned

@bobheadxi: 6.00d

Completed: 6.00d

@mollylogue: 18.00d

Completed: 17.00d

@ryanslade: 41.00d

Completed: 41.00d

@sashaostrikov: 26.00d

Completed: 26.00d

@varsanojidan: 1.00d

Completed: 1.00d

Legend

  • 👩 Customer issue
  • 🐛 Bug
  • 🧶 Technical debt
  • 🎩 Quality of life
  • 🛠️ Roadmap
  • 🕵️ Spike
  • 🔒 Security issue
  • 🙆 Stretch goal
  • :shipit: Pull Request