Review Board supports posting and reviewing code on GitHub repositories, using public or private personal repositories or organization-owned repositories.
Existing commits in a repository can be browsed and put up for review. Pull requests, however, are not currently supported (though planned for a future release).
To simplify posting changes to Review Board, we recommend using RBTools. This ensures that the diffs are in the correct format, and makes managing review requests much easier. See Using RBTools with Git for more information.
Adding the Repository¶
To configure a GitHub repository, first proceed to add the repository and select GitHub from the Hosting type field.
Step 2: Provide Repository Information¶
Next, you’ll need to fill out the following fields:
- Repository plan:
This specifies the type of the repository, whether it’s public/private or personal/team. You’ll have one of the following choices:
- Public: The repository is owned by the linked user account, and is publicly-accessible to any user.
- Public Organization: The repository is owned by an organization, and is publicly accessible to any user.
- Private: The repository is owned by the linked user account, and is accessible only to the linked user and other GitHub users who were granted permission.
- Private Organization: The repository is owned by an organization, and is accessible only to the linked user and other GitHub users who were granted permission.
The public/private options have no bearing on who can access review requests on this repository in Review Board. See Step 4: Manage Access Control.
- Organization name:
- If you’re using an organization-based plan, you will need to specify the
organization name in the Organization name field. This is the
same value you would find in the URL. For example, if your repository was
https://github.com/myorg/myrepo/, your organization name would be
- Repository name:
- You’ll then need to specify the name of your repository in the
Repository name field. This is the same value you would find
in the URL. In the above example, your repository name would be
Step 3: Choose a Bug Tracker¶
If you’re using the issue tracking feature on this repository, you can simply check the Use hosting service’s bug tracker checkbox. All bug IDs will link to the appropriate issues for your repository.
If you’re using a separate bug tracker, or a separate repository on GitHub, you can leave the checkbox unchecked and choose a bug tracker from the list.
Step 4: Manage Access Control¶
You can now choose who should have access to this repository (both posting against it and viewing review requests posted against it). This is separate from GitHub’s own access controls.
Step 5: Save the Repository¶
At this point, you should be able to save the repository. If saving succeeds, you’re done! You can start posting changes for review.
If you’re using RBCommons or have a custom GitHub OAuth application for your Review Board installation, you may see an error that the repository could not be found. This can happen if your GitHub organization requires access to be granted per-app, which is the default for modern organizations.
See Granting Organization Access to fix this, and then save the repository again.
Configuring Repository Hooks¶
Review Board can close review requests automatically when pushing commits to GitHub. This is done by configuring a WebHook and pointing it to your Review Board server, and then referencing the review request in your commit message (which is done for you when using rbt land).
Let’s go over how to set this up.
Your Review Board server will need to be accessible over the Internet for this to work. GitHub will be performing HTTP/HTTPS requests to your server to notify Review Board of new commits.
Add the WebHook¶
On Review Board, view the list of repositories and locate the repository you want to configure hooks for. Beside the repository name, you’ll see a Hooks link. Click that and you’ll see instructions for configuring the hook.
The instructions will contain a link taking you to the page on GitHub for adding a new WebHook, along with all the information you need in order to add the hook. Simply follow the instructions and you’ll be ready to go.
Tag Your Commit Messages¶
To close a review request for a given commit, you’ll need to add some special
text to your commit message that references the review request. This can be in
the form of
Reviewed at review_request_url or
#id. This must be on its own line, but can appear anywhere in the commit
Reviewed at https://reviewboard.example.com/r/123/
Review request #123
If you use rbt land, this will be automatically added for you when landing your changes.
Registering Custom GitHub OAuth Apps¶
If you’re running a large Review Board server with a lot of activity on a few particular repositories (hundreds or thousands of review requests posted per hour), you may want to register a custom GitHub OAuth app for your Review Board server.
This is advanced usage and is completely optional! Most servers do not need this. You may need to redo your OAuth app settings in a future Review Board release as well.
You would only want a custom app if you’re hitting errors saying you’ve gone over your GitHub API access limit for the hour.
To register an application, visit the Register a new OAuth application page and specify:
- Application name:
Review Board for <your company>
- Homepage URL: Your Review Board server’s URL.
- Authorization callback URL:
Click Register application. You will then see two new sets of
credentials: Clent ID and Client Secret. You’ll need
to put these in your Review Board install’s
This should look like:
GITHUB_CLIENT_ID = '<Client ID value>' GITHUB_CLIENT_SECRET = '<Client Secret value>'
Restart Review Board and then re-link any accounts being used by repositories.
Granting Organization Access¶
In order to keep your code secure, GitHub organizations are often set to require that third-party applications, like RBCommons or custom GitHub OAuth applications, have their access explicitly granted by an organization administrator. This is the case by default with newer organizations, and many older ones have this on as well.
If you’ve tried to link one of your GitHub organization’s repositories to RBCommons or to a server with a custom GitHub OAuth application defined, you may have received an error message stating that the repository could not be found. This may simply mean that the server doesn’t yet have the permission to access it.
In this guide, we’ll help grant access.
Step 1: Verify Your Access Settings¶
You’ll need to check whether your organization restricts new third-party applications.
Have a GitHub organization administrator navigate to your organization page
https://gthub.com/orgname) using their admin account. Click
Settings and then click Third-party access on the
From here, you’ll be able to see the current access policy and any approved applications.
If Policy says Access restricted, then continue on with this guide.
However, if it says No restrictions, then you don’t need to worry about this guide, and should double-check the information you entered into the repository form instead (if it gave you an error about not being able to find your repository).
Keep this page handy. You’ll need to come back to it.
Step 2: Request or Grant Access¶
Make sure you’re logged in as the user whose account was linked to Review Board when configuring the repository. Go to your settings page (click your avatar in the top-right of any page on GitHub, and then click Settings). Then click Applications on the left.
“RBCommons” (or the name of your custom application) should appear in this list under Authorized Applications. Click on it.
From here, you’ll see a list of organizations you belong to that have access to your application, and any that need access to be granted. Your organization should appear in this list along with a button for requesting or granting access.
If you’re an organization admin…¶
Click Grant access from here. You’re done! Go back and save your repository again, and you should be all set up.
If you’re not an organization admin…¶
Click Request access and follow the instructions. You’ll then need to continue with step 3.
Step 3: Approve Requested Access¶
If you clicked Request access above, you’ll now need an organization admin to approve it (by clicking Grant Access above). The administrator from Step 1 should reload the page they were on in that step. RBCommons (or your custom application) should now be in the list. Simply approve the application from there, and you should be good to go.
Then, simply save the repository again. You’re done!