Setup source repository integration
Your source files should be encoded in UTF-8 in order for Mingle's integration to work properly. Otherwise you may see odd characters showing up in the Mingle Source tab as Mingle is unable to decode the file correctly.
Getting started
To connect your project to your source repository, select the Project admin tab, Project repository settings link. Mingle will display the Configure project repository page
Select a version control system from the list presented
Then follow the instructions below to configure integration with your chosen repository
Subversion source integration
After choosing Subversion from the source repository list, Mingle will display the Subversion Repository settings page
- Enter the URL for your subversion repository. Most standard SVN URL schemes are supported by Mingle 2.0, including local file access if the repository is located on the same filesystem as Mingle. New in 2.0, Mingle can integrate your project with a subdirectory of your SVN repository. This allows Mingle to work better with multi-project SVN repositories.
- If your repository requires username and password authentication, be sure to enter that information as well. You must first click the Change login user password to enter a new password.

Click the Save link to save the configuration and return to the Project admin page
Checking that source repository integration is working correctly
To verify that the source repository integration is correctly configured, open the Mingle Source. You should see a series of links that represent the subdirectories within your source repository. You can drill down inside these links to find specific files.
Within a few minutes of saving your new source configuration you will start seeing revisions in your project history. You can use the card keywords feature to integrate your revisions with individual Card history. You can change these keywords at any time and the revision-to-card links will be completely rebuilt, starting with the first revision. If you start with a working or legacy repository, you can tweak the keywords to match any patterns you may have used in those older commit messages.