1. Login to stash: https://stash.uconn.edu/
2. Navigate to FEB Nitro Files (FNF) project
3. Provided you have the necessary privileges, click on the "Create repository" button, top-right
   Image Modified
4. Provide an appropriate name and then click on the "Create repository" button
   Image Modified
5. Clone repository to local
   1. Use git/bash command:
      Make sure you are inside the project folder of where you want to clone and then execute the following command:
      git clone REPOSITORY_URL
      Image Modified
6. Open up Sourcetree software
7. Add a new repository, by clicking on the "+" at the top:
   Image Modified
   
   1. Click on Add at the top:
      Image Modified
   2. Click on "Browse"
      Image Modified
   3. Navigate to where you cloned locally (Step 2.a., above)
   4. And click on "Select Folder" ---- ensure that the folder you select has a .git folder (this is a hidden folder — so you might not see it, based on your settings), as shown below
      Image Modified
   5. Finally, click "Add"
      Image Modified
8. Go to Leap TEST environment and export the project (if you have not done it already) and save it locally
9. Locate the *.nitro_s file and move it to this folder (same folder as 2.a., above)
10. Sourcetree will notice a change in the local repository and list it under "Unstaged files" section
    Image Modified
11. Select either "Stage All" or "Stage Selected", depending on your circumstance
12. Under comments, follow the following format (without quotes):
    "JIRA XXX-###
    YOUR COMMENTS"
    " (where XXX is the project key, in Jira and ### is the ticket number; you can provide your comments after that)
13. Next, make sure you select the "Push changes immediately to..." checkbox
14. Finally, hit the "Commit" button.
    

    Example of Steps 9 - 11:

    Image Modified

15. Next, create a tag, by clicking on "master" under "BRANCHES" on the left
    Image Modified
16. Right-click on the blue line and select "Tag..."
    Image Modified
17. Give it an appropriate name; generally, this convention should work: "NAME_OF_REPO_v#.#" (where #.# is your version number e.g. 1.0, 1.1, etc.)
    Image Modified
18. Notify that the tag has been created and it's ready to go live.

@DEVELOPER NAME

•  JavaScript files: using minified versions?
•  Confirm Security/Access Control (as reflected on THIS page)
•  Update Jira Ticket
•  Stash component
•  Queued for Go-Live! / Notify Jason Card
•  Update project's requirements page on Confluence
•  Notify customer/team post deployment with relevant link(s)