Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,459,458
Community Members
 
Community Events
176
Community Groups

Amount of code reviewer

Edited
ady magal
ady magal Jan 28, 2019

Hi,

we are establishing our internal process of code review using BitBucket and have two approaches:

1. Have mandatory 2 reviewer where the 1st one is any developer who got approval for code review and the second is one of few experts we have in the company.

2. Have one reviewer that is mandatory and another reviewer that is optional, the expert will review some of the pull request and provide feedback on the code review

What are the industrial best practices? 

:)

Comment
Watch
Like Be the first to like this
313 views

0 comments

Comment

Log in or Sign up to comment
Bitbucket
Bitbucket
TAGS

Atlassian Community Events

See all events