Jump to >

This documentation covers Review Board 2.5. You can see the latest Review Board documentation or all other versions.

Gitorious Repositories

Review Board supports posting and reviewing code on Gitorious 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 Gitorious repository, first proceed to add the repository and select Gitorious from the Hosting type field.

Step 2: Provide Repository Information

Next, you’ll need to fill out the following fields:

Project name:

The project name that hosts the repository on Gitorious. This must be the name found in the clone URL.

For example, if your repository was at https://gitorious.example.com/myproject/myrepo, your project name would be myproject.

Repository name:

The name of the repository. This must be the name found in the clone URL.

For example, if your repository was at https://gitorious.example.com/myproject/myrepo, your project name would be myrepo.

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 Gitorious, you can leave the checkbox unchecked and choose a bug tracker from the list.

Learn more about bug tracker configuration.

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 Gitorious’s own access controls.

Learn more about access control.

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.