What differentiates the app from the native Code Owners feature of Bitbucket Data Center?

auto-assignment of reviewers

✅

✅

• file/ folder path patterns

✅ 🔗

/features/FeatureCode.java @developer

✅

/features/FeatureCode.java @developer

• file extension patterns

✅ 🔗

**.css @developer

✅

**.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

✅ 🔗

@developer
@"Paul the JSGuru"
paul@example.com

✅

@developer

• assign user groups

✅ 🔗

@@developers

• Bitbucket groups

• Bitbucket reviewers groups

• custom groups defined in CODEOWNERS file

❌

• assign random subset of reviewers

✅ 🔗

CODEOWNERS.toplevel.assignment_routing random 2

❌

• custom merge checks

✅ 🔗

# At least a 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

❌

Flexible configuration

✅

❌

• Enable/disable per project

✅

❌

• Enable/disable per repository

✅

❌

• mono-repos support (possibility to have different CODEOWNERS files in different folders)

✅

❌

auto-merge of PR

✅ 🔗

✅ 🔗

ship/show/ask support

✅ 🔗

❌

support draft PR

(no reviewer assignment until PR is ready to review)

✅ 🔗

✅ 🔗

Code Owners Playground for interactive experimentation

✅ 🔗

❌