If you do not already have SourceTree you can download it at https://www.sourcetreeapp.com/.
Once you install the SourceTree software log on to UConn’s central Git repository https://stash.uconn.edu/projects
Step-by-step guide
Getting Starting with Git and SourceTree
Click on the Kuali Financial System link
then the dbscripts link
Click on the Clone link under the ACTIONS heading on the left side of the page this will display a dialog box with a “Clone In SourceTree” option. This is a one time procedure that will create a local copy of the repository and link it to the main dbscripts repository.
Click on the Clone In SourceTree button it will let you specify where your local repository will be located. When you decide click Clone. This will clone the repository and open SourceTree on your workstation.
In SourceTree click on the Branch icon on the menu bar
- In the New Branch area enter the name of your branch (please include your net-id in the name) and click Create Branch. The branch name will appear under the Branches heading on the left.
- Double click on the branch name. This is now your working branch you will create all your scripts here. Please note that the branch will not be noticeable in the directory structure, Git keeps track where you are working and keeps your branch isolated from the master repository.
- In the New Branch area enter the name of your branch (please include your net-id in the name) and click Create Branch. The branch name will appear under the Branches heading on the left.
Committing you scripts.
It is critical that you save each script in the correct directory. You should save scripts to run in the KFS schema in the kfs-scripts directory and likewise scripts for the Rice(KR) schema in the kr-scripts directory. After testing you can commit your scripts to the Git repository as follows:
Open SourceTree
Make sure your branch name under the BRANCHES heading is highlighted
Click on the Uncommitted changes line under the Description heading on the top of the page. You should see the file you created listed under the Unstaged files heading. The line with the
icon indicates new files ready to be staged. 
Click the box next to the file and it will migrate the Staged files section.
Click the Commit icon (top left of the page)
Enter the Jira ticket number and brief description on the script. Do not forget to click the Push changes… box under the description area then click on the Commit button on the lower right of the screen. If you do not the changes will not be sent to the central Git server at the same time. If you do forget you can click on the Push icon on the upper left which will send the changes.
The scripts are now ready to be reviewed and staged for execution by the uconnScriptRunnerJob batch job.