Improve the quality of your code reviews by automatically assigning code owners as mandatory pull request reviewers
Improve the quality of your code reviews by automatically assigning code owners as mandatory pull request reviewers
Improve the quality of your code reviews by automatically assigning code owners as mandatory pull request reviewers
Use version-controlled files for reviewer rules
Reviewers are automatically added to pull requests
Prevent merges not reviewed by code owners
Just put a file called CODEOWNERS in your repository with a list of pull request reviewers you want for specific file patterns. These reviewers are called code owners who are experts in a specific code area.
This app adds code owners as mandatory reviewers to new pull requests automatically. It also supports reviewer groups for easier maintenance. And for multiple projects in a repository, it has subdirectory overrides.
The app has merge checks to only allow merging a pull request when a configured number of code owners have reviewed it. It also allows configuring that only some group members must review a pull request.
Use version-controlled files for reviewer rules
Reviewers are automatically added to pull requests
Prevent merges not reviewed by code owners
Just put a file called CODEOWNERS in your repository with a list of pull request reviewers you want for specific file patterns. These reviewers are called code owners who are experts in a specific code area.
This app adds code owners as mandatory reviewers to new pull requests automatically. It also supports reviewer groups for easier maintenance. And for multiple projects in a repository, it has subdirectory overrides.
The app has merge checks to only allow merging a pull request when a configured number of code owners have reviewed it. It also allows configuring that only some group members must review a pull request.
More details
Code reviews are an important part in successful software projects, but it's not always clear who should review a pull request. With this app, repository maintainers can configure which persons and groups need to review a pull request using the concept of code owners.
Code owners are engineers who own a specific code area. They are people who know this area of code really well and are very interested that the code quality stays great. The main idea is that if a developer provides a bug fix or a new feature, the change in that code area gets reviewed by the responsible code owner.
To configure this mapping between code owners and files, the app uses a configuration file called CODEOWNERS. Here's an example: to make sure that all React.js components will be reviewed by the team "ReactGurus", you can define a rule in the file CODEOWNERS like follows:
/src/components/**/*.js @@ReactGurus
The app will then make sure that somebody from that team will review changes in these components.
More details
Code reviews are an important part in successful software projects, but it's not always clear who should review a pull request. With this app, repository maintainers can configure which persons and groups need to review a pull request using the concept of code owners.
Code owners are engineers who own a specific code area. They are people who know this area of code really well and are very interested that the code quality stays great. The main idea is that if a developer provides a bug fix or a new feature, the change in that code area gets reviewed by the responsible code owner.
To configure this mapping between code owners and files, the app uses a configuration file called CODEOWNERS. Here's an example: to make sure that all React.js components will be reviewed by the team "ReactGurus", you can define a rule in the file CODEOWNERS like follows:
/src/components/**/*.js @@ReactGurus
The app will then make sure that somebody from that team will review changes in these components.
Reviews for cloud
(8)Sign in to write a reviewThere are no reviews yet. Be the first to review this app.
Reviews for server
(8)Sign in to write a review
Thank you for your feedback. Please note that you must protect your CODEOWNERS file by a separate rule so that pull requests cannot delete it. Here's an example of how you can accomplish this:
CODEOWNERS @TeamLead
With this, a CODEOWNERS file could only get deleted if the responsible code owner (TeamLead) accepts the pull request.
We will improve the documentation regarding this to make this more clear.
Please contact us via our support address if you have other issues.
Best regards,
Michael from Mibex Software
Thank you for your feedback.
Please find the documentation with examples in our Wiki.
We cannot see an issue in terms of security here because only users with permissions to the target branch of a pull request (e.g., "master") can change an existing code owners configuration. So all that is necessary is the appropriate branch permissions in the Bitbucket repository configuration. But we are also thinking about an optional configuration inside the CODEOWNERS file to only allow certain users to change it.
The approvals of code owners are not separate from the approvals of normal pull request reviewers. So they count towards the number of approvals because code owners are also reviewers. But the app also provides its separate merge checks which are based solely either on individual code owners or groups of code owners. You can find them under Repository Settings -> Merge Checks -> Code Owners minimum approvals.
Please contact us via our support address if you have further issues or improvement ideas.
Best regards,
Michael from Mibex Software
Reviews for Data Center
(8)Sign in to write a review
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$50 | 50 users$100 | 100 users$150 | 250 users$250 | 500 & upAdditional pricing details |
| 25 users$50/year | 50 users$100/year | 100 users$150/year | 250 users$250/year | 500 users$500/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. The app tier should match the licensed user tier of the Atlassian product. For example, if you have a Confluence license for 500 users, you should purchase the 500-user tier for apps. Even if fewer users want to use the app than your Atlassian product license, the two licenses should match exactly.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Apps are billed based on the number of users in your Atlassian product. The app tier should match the licensed user tier of the Atlassian product. For example, if you have a Confluence license for 500 users, you should purchase the 500-user tier for apps. Even if fewer users want to use the app than your Atlassian product license, the two licenses should match exactly.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
Mibex Software GmbH provides support for this app.
Mibex Software GmbH provides support for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 2.4.0 • Bitbucket Server 5.2.0 - 7.4.0 • Released 2020-07-03
Summary
Subdirectory overrides, destination branch support and optional PR comment
Details
New features:
- Subdirectory overrides: You can now enable subdirectory overrides, allowing subdirectories to have their own Code Owners files. This is great if there are multiple projects in a shared repository and each project needs to manage their own Code Owner rules.
- Destination branch activation: Per default, a Code Owner file affects pull requests for all destination branch names. You can now make a Code Owner file to only apply pull requests with specific destination branches.
- Disable Code Owner comments: By default, Code Owners adds a comment with the code owners of the pull request and the reason for inclusion. If you don’t need this comment and want fewer notifications, you can now disable it.
Versions
Version 2.4.0 • Bitbucket Data Center 5.2.0 - 7.4.0 • Released 2020-07-03
Summary
Subdirectory overrides, destination branch support and optional PR comment
Details
New features:
- Subdirectory overrides: You can now enable subdirectory overrides, allowing subdirectories to have their own Code Owners files. This is great if there are multiple projects in a shared repository and each project needs to manage their own Code Owner rules.
- Destination branch activation: Per default, a Code Owner file affects pull requests for all destination branch names. You can now make a Code Owner file to only apply pull requests with specific destination branches.
- Disable Code Owner comments: By default, Code Owners adds a comment with the code owners of the pull request and the reason for inclusion. If you don’t need this comment and want fewer notifications, you can now disable it.
Installation
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Code Owners for Bitbucket Server via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Code Owners for Bitbucket Server. You're prompted to log into MyAtlassian. Code Owners for Bitbucket Server begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.
To find older Code Owners for Bitbucket Server versions compatible with your instance, you can look through our version history page.
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Code Owners for Bitbucket Server via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Code Owners for Bitbucket Server. You're prompted to log into MyAtlassian. Code Owners for Bitbucket Server begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.
To find older Code Owners for Bitbucket Server versions compatible with your instance, you can look through our version history page.
Similar apps
