nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CODEOWNERS does not work

Bruno Silva_zyc6mv

Hello,

I am trying to set up code owners in our repository.

I followed the following documentation but it seems not to work:

https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-code-owners/

The file structure looks like the following:

.bitbucket/
    CODEOWNERS
    teams.yaml

In the `teams.yaml` file, I have the following content:

frontend:
  contributors:
    - user1@domain.com
    - user2@domain.com
    - user3@domain.com
reviews:
    strategy: least_busy
select: 3

In the `CODEOWNERS` file, I have a content similar to this:

/resources/js   @teams/frontend

However, no one is assigned as a reviewer when I open pull requests targeting the destination branch with the code owners setup.

Alternatively, I also tried setting up a group using the `@<workspace-slug>/<group-name>` syntax and even adding the emails directly to the CODEOWNERS file but had no success as well.

Am I missing something?

Thanks in advance!

Accepted answers

Theodora Boudale

Hi Bruno and welcome to the community!

Are there changes in the files of the directory /resources/js in the PR's source branch?

I tried reproducing this with a teams.yaml file and a CODEOWNERS file similar to yours and the reviewers are added when I try to create a PR.

If there are changes in the directory /resources/js, I would suggest creating a ticket with the support team for further investigation. If we have an open support ticket, the engineer working on it will be able to access the repo, double-check if anything is missing from the configuration, and investigate what is causing this.

You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.