Jump to >

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

Unfuddle STACK Repositories

Review Board supports posting and reviewing code on Unfuddle STACK repositories.

The following types of Unfuddle STACK repositories are supported:

  • Git
  • Subversion

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.

Adding the Repository

To configure an Unfuddle STACK repository, first proceed to add the repository and select Unfuddle from the Hosting type field.

Step 2: Provide Repository Information

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

Repository type:
The type of repository you’re adding. This can be either “Git” or “Subversion”.
Unfuddle account domain:
Your Unfuddle STACK domain. This would be the domain_name in https://domain_name.unfuddle.com/.
Unfuddle project ID:

The numeric ID for your project, found in the URL on your Project page.

This would be project_id in https://domain_name.unfuddle.com/a#/projects/project_id.

Repository name:
The name of your repository, as you’d see it in the checkout/clone URL. This is not the customizable display name.

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 domain or project ID Unfuddle STACK, 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 Unfuddle STACK’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.