-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Readme should document what this repo about and how it's related to product-apim #7826
Comments
Camille0183:patch-1components/apimgt/org.wso2.carbon.apimgt.api/src/main/java/org/wso2/carbon/apimgt/api/model/Monetization.java..usagwSkip to main content Who can use this feature Code review settings are available in all public repositories owned by an organization, and all private repositories owned by organizations on GitHub Team, GitHub Enterprise Server 2.20+, and GitHub Enterprise Cloud. For more information, see "GitHub's products." About code review settings Team notifications About auto assignment When code owners are automatically requested for review, the team is still removed and replaced with individuals unless a branch protection rule is configured to require review from code owners. If such a branch protection rule is in place, the team request cannot be removed and so the individual request will appear in addition. Routing algorithms The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period. Any team members that have set their status to "Busy" will not be selected for review. If all team members are busy, the pull request will remain assigned to the team itself. For more information about user statuses, see "Setting a status." Configuring team notifications Click the name of your organization. Under your organization name, click Teams. Teams tab On the Teams tab, click the name of the team. At the top of the team page, click Settings. In the left sidebar, click Code review. Select Only notify requested team members. Click Save changes. Configuring auto assignment Click the name of your organization. Under your organization name, click Teams. Teams tab On the Teams tab, click the name of the team. At the top of the team page, click Settings. In the left sidebar, click Code review. Select Enable auto assignment. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "Routing algorithms." Optionally, to always skip certain members of the team, select Never assign certain team members. Then, select one or more team members you'd like to always skip. Optionally, to include members of child teams as potential reviewers when assigning requests, select Child team members. Optionally, to count any members whose review has already been requested against the total number of members to assign, select Count existing requests. Optionally, to remove the review request from the team when assigning team members, select Team review request. Click Save changes. Disabling auto assignment Click the name of your organization. Under your organization name, click Teams. Teams tab On the Teams tab, click the name of the team. At the top of the team page, click Settings. Select Enable auto assignment to remove the checkmark. Click Save changes. Did this doc help you? Privacy policy Or, learn how to contribute. Still need help? |
Readme file on this repo should document,
Right now it's very hard for a new developer to look at this repo and figure out the relationship/importance
The text was updated successfully, but these errors were encountered: