CODEOWNERS not working

[Gaspar Oliveira]

Hi, 

I've followed this tutorial (https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-code-owners/) on how to setup code owners on my repository but is not working. 

After creating the file and having it on the main branch, the owners are not visible on the right sidebar, the option to set code owners on a merge check and on a new pull-request the default reviewers from the CODEOWNERS file are added as default reviewers.

I've tried these configurations but with the same unsuccessful result:

- ./bitbucket/CODEOWNERS using user@email.com

- ./bitbucket/CODEOWNERS using user@email.com and teams.yaml

- ./bitbucket/CODEOWNERS using @TeamS/name and teams.yaml

Regarding my setup, I have Bitbucket Cloud with Premium price plan. The users login via Google SSO.

[Arkadiusz Wroblewski · Accepted solution]

Hello @Gaspar Oliveira 

The most likely issue is a "tiny tiny tiny" typo in your folder path. Bitbucket won't recognize `./bitbubeck/CODEOWNERS`; it must be exactly `.bitbucket/CODEOWNERS` at the repository root.🫣

Also, keep in mind that Bitbucket reads this file from the *target* branch, meaning the code ownership rules must already exist on your destination branch to trigger for new PRs. If your path is fine, double-check your syntax: workspace groups require the `@workspace-slug/group-slug` format, and custom teams via `teams.yaml` use `@teams/team-name`. Try testing a simple wildcard rule like `* email@example.com` to see if it hooks in.

Best,

Arkadiusz🤠

[Gaspar Oliveira]

Hi @Arkadiusz Wroblewski 

thank you for the reply.

The typo was only on the post not that path 😅 i've updated the post to fix that.

I've also updated the usage of the teams on the post because it also had a typo.

My last attempt was to only have a single line on the CODEOWNERS file like:
/directory-name/** user@email.com

this is still not working, but I can try to set it do the wildcard to see if it triggers it.

[Gaspar Oliveira]

After setting the wildcard it worked. After that I was able to set the file with the necessary setup to work as I wanted.

Thank you for the help

[Arkadiusz Wroblewski]

@Gaspar Oliveira 

No need to thank us! 😊

We're here for the community and for helping each other out.

Have a great day ☀️

Arkadiusz 🤠