CODEOWNERS on project level?

Question

Hi!

I wanted to ask if it would be somehow add people to codewners group on project level even if the person does not have access to all of the repos under that project? It seems it's not currently possible.

I'm actually working in a company that has it's own https://bitbucket.company.tools/ Bitbucket. There's project that has lot of repos, but then I and some other devs have access to only about 10. It would be nice if there was one place to create some groups, then add them via the CODEOWNERS file. Now it seems we need to manage them repoy by repo.

Hannes Kirsman · Answer

It might help in some cases where config needs to unified, tx!

I think it would not help in case you have set user to multiple repos to a group and then you have to remove them at some point so you'd have to do it multiple times.

Michael Rüegg _Mibex Software_ · Answer

As my colleague Roman mentioned, we have been working on a tool that allows you to share common configurations like Code Owners across repositories.

This tool is now available and it is called DevSensei Pull Request Workflow Automation. Its configuration is YAML-based in a file called devsensei.yaml, so you have all the advantages of configuration as code.

By using Bitbucket reviewer groups, you can configure your reviewers on a project level (see example below: frontendTeam).

And you can even share your Code Owner rules across repositories of your project by including workflows from another repository.

Here's an example:

commons/devsensei.yaml

workflows:
  - name: Add Code Owners
    conditions:
      - destination=develop
    actions:
      - add-codeowners:
        rules: |
@frontendTeam

repo_a/devsensei.yaml

includes:
  - commons/devsensei.yaml

repo_b/devsensei.yaml

includes:
  - commons/devsensei.yaml

Does that help you? You can find more information in the docs.

Best,
Michael from Mibex (app vendor of DevSensei Pull Request Workflow Automation)

Roman Stoffel · Answer

Ok: So copying the CODEOWNERS file is fine at the moment.

So, in Codeowners for Bitbucket (the app, not the built in functionality), the groups can are also resolved again Bitbucket Reviewer Groups (DC), which can be defined on project or repo level.

So, in Bitbucket DC you then can have CODEOWNER files at repository level reference these reviewer groups. And update the reviewer groups at project level with new members / remove members.

On Bitbucket Cloud there is afaik no such concepts yet. There are Groups on the Workspace level, and those are used.

That are the solutions approaches that I am aware of.

PS: As mentioned we are working on more 'Project oriented' CodeOwner features for the app =) . But that is in its design phase =) .