# Working on a tenant
Marfeel's clients each have their own GitHub repository, named after the Media Group name. There are more details about the tenants' site repositories in the Continous Deployment overview.
# Clone a tenant site repository
Use the glue clone command to clone a repository using the tenant's URL. Your insight token must be configured (part of the automatic setup from mrf-env -a).
$ glue clone -t www.example.com ## `-t` for `tenant`
Looking for token: /Users/user/.mrf/insightToken.txt
Received 1 git repositories to process
Cloning repository: git@github.com:Marfeel/MediaGroupExample.git into /Users/user/Marfeel/AliceTenants/MediaGroupExample
Cloning into 'MediaGroupExample'...
remote: Enumerating objects: 16, done.
remote: Counting objects: 100% (16/16), done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 2535 (delta 5), reused 7 (delta 3), pack-reused 2519
Receiving objects: 100% (2535/2535), 542.63 KiB | 1.88 MiB/s, done.
Resolving deltas: 100% (1675/1675), done.
Symlink creation /Users/user/Marfeel/AliceTenants/Tenants/vhosts/www.example.com // /Users/user/Marfeel/AliceTenants/MediaGroupExample/www.example.com
See other available options of glue clone here.
# Branching & Committing
Once in the tenant repository, create a branch with the ticket name as prefix, as explained in the demo training:
git checkout -b GOL-123-awesome-feature
Once ready, push the branch to the repository origin:
git push origin GOL-123-awesome-feature
# Pull request process
Run glue open:repository to open the pull request page directly.
A review from another marfeeler is required in order to merge: the master branch is always protected.
# Deploying a site
Once you merge, the build starts on Jenkins (opens new window).
Code is automatically deployed once the build passes.
# Checking for errors
Check the anomalies dashboard (opens new window) filtering for the tenant which you just deployed.