Michael Rüegg
Apr 03, 2024
...
Feature
Code Owners for Bitbucket app
Bitbucket native Code Owners feature
file/ folder path patterns
✅ 🔗
/features/FeatureCode.java @developer
✅
file extension patterns
*.css @developer
exclusion patterns
frontend/* @frontend-team # no mandatory review for tests !frontend/*/tests/**
❌
Match options of patterns
src/{main/**,test/**} @devs **.{ts,js} @web-devs
assign user
Display Name
Nickname (Public name) of Bitbucket Cloud users
NOT supported:
e-mail addresses or user slugs
foo.py @"Michael Foo"
foo.py individual@example.com bar.py @individual-username baz.py @workspace-slug/group-name
assign user groups
src/** @@developers
Bitbucket Cloud groups
custom groups defined in CODEOWNERS file
CODEOWNERS
@@@<newgroupname> <members>
custom groups defined in teams.yml:
teams.yml
backend: contributors: - individual1@example.com - individual2@example.com
assign random subset of reviewers
CODEOWNERS.toplevel.assignment_routing random 2
*.scala @workspace-slug/reviewer-group:random(2)
assign least busy (have the fewest active PR reviews) reviewer assignmentreviewers
*.scala @workspace-slug/reviewer-group:least_busy(2)
custom merge checks
# At least aone senior and two code owners in total must approve. OverallCheck(2) Check(@@Seniors >= 1)
Fallback groups(users who can be added as reviewers and whose approval counts for merge checks in case of code owners absence)
✅ 🔗 ✅ 🔗
@@@FallbackOwners @paul @monica
mono-repos support(: possibility to have different CODEOWNERS files in different folders)
Code Owners Playground for interactive experimentation