Unfuddle STACK Repositories¶
Review Board supports posting and reviewing code on Unfuddle STACK repositories.
The following types of Unfuddle STACK repositories are supported:
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 1: Link Your Unfuddle STACK Account¶
You will need to link an account on Unfuddle STACK to Review Board, so that Review Board can access content from the repository. If you’ve already linked an account with sufficient access to the repository, you can use that instead.
If you’re linking for the first time, you’ll need to make sure you have your username and password handy.
Fill out the following fields:
- Account username:
The username used to log into your Unfuddle STACK account. This is not your e-mail address.
- Account password:
The password used to log into your Unfuddle STACK account.
Due to the way the Unfuddle STACK API must be accessed, your password will be stored in encrypted form in the database.
The account will be linked when the repository is saved. If there are errors authenticating the user or retrieving an access token, you will be prompted to fix them.
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
- Unfuddle project ID:
The numeric ID for your project, found in the URL on your Project page.
This would be
- 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.
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.
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.