1

My company has the notion of a Senior Tier of developers. These developers are dispersed amongst development teams. Then we assign the Senior Developers from one team to assess the contribution from a different team they were assigned.

Let's say I have a project foo and for foo, I want

  • SeniorBarGroup to review PRs to BazGroup, and
  • SeniorBazGroup to review PRs to QuzGroup

Is this workflow possible in GitLab?

Improve this question
4
  • 1
    What about CO - docs.gitlab.com/ee/user/project/code_owners.html
    – Kyslik
    Jun 21, 2022 at 14:10
  • @Kyslik Right from the get go, that doesn't sound like what I want (I may be missing something). "Code Owners define who owns specific files or directories in a repository.". That's what everyone does. We don't have "code owners" at $work though. We have team owners. Two senior devs owns the contributions of another team, regardless of files or directories.
    – Evan Carroll
    Jun 21, 2022 at 15:34
  • 1
    I think neither GH or GL support what you want. Even if you automate and "request" review from correct teams (using API or GraphQL), GL won't enforce it the same way how CO works.
    – Kyslik
    Jun 21, 2022 at 16:44
  • According to this source, there is no native functionality in GitLab to help assist in assigning a reviewer based on the contributor. However, you can model this relationship external to GitLab.
    – Baft Tabaku
    Jul 16 at 21:02

1 Answer 1

Reset to default
0

I don't believe there is any native functionality to help assist in this, and that this relationship will have to be modeled external to GitLab. I've opened this issue for clarity,

https://gitlab.com/gitlab-org/gitlab/-/issues/365887

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.