If the following documentation can't help solve your issue, please feel free to contact us!


Initializes a jet repository. This is the first command you should type into the command line to start using Jet.
$jet init


This command adds new, deleted and changed files to the changeset, ready to be committed.
$jet add


This pushes the latest code, commits and changes to the server, ready for other people to borrow / browse / use. Appending the message onto the command is great practise and should be used. This allows others to see what you meant with your changes.
$jet push
$jet push -m <your message>


This merges the branch you enter with the current branch you are in. This command will also do a commit, to save the process of merging. To see the current branch you're on, use the status command. Make sure you have committed before using this.
$jet merge <branch_name>


This command gives you detailed information about each commit, what files were changed and what happened to them. The commit number is the commit you're interested in, and the line number is the change you'd like to find out more information on. To find out which line numbers are associated to which change, simply omit that field. Omitting the line number and commit number will result in a list of all commits being printed.
$jet list
$jet list <commit_number>
$jet list <commit_number> <line_number>


A branch is a separate copy of the repository where you can work on new features, bug fixes or just keep things separate. This command makes a new branch.
$jet branch <branch_name>


Gives a list of the current branches being used and gives their parent in brackets.
$jet branches


Permanently deletes the given branch
$jet delete <branch_name>


Switches to the given branch. You must have committed all changes before switching.
$jet switch <branch_name>


Reverts the repository to the state of the branch and commit number specified. This command is irreversible, and a confirmation is required. Use the list command to obtain information on where to switch to.
$jet revert <branch_name> <commit_number>


Gives a list of all files which have unresolved merge conflicts. These must be resolved using the resolve command before committing.
$jet conflicts


This command checks the current status of your repository. It will print out in green which files are new, red deleted files and in orange any edited files. Jet will also print the contents of the current changeset, as discussed in 'Add'. The branch you are working on will also be printed.
$jet status


This command will print out the difference between the current contents and the contents at a particular point in the commit history of a file. The filename argument is the file to be compared. The branch and commit number is the place in the history to compare it to.
$jet diff <filename> <branch> <commit_number>


This will pull the latest changes saved to the server down to your computer. This command can cause merge conflicts, so ensure you haven't edited the same part of any files which have been changed. To overwrite your local copy with what's on the server, just append '-f' to the command
$jet pull
$jet pull -f


This will take any changes added to the changeset (using $jet add) and make a record of what was changed, and by who - this is then a point in to which the files could be reverted or released. Make sure to add a meaningful message between the quote marks, to show why you did the change.
$jet commit -m "Insert message here"


This will test jet is in full working order. Ensure it says all tests pass. If any fail, please try reinstalling jet.
$jet test


Logs you into jet. This enables your username to be placed alongside commits, to see which ones you did.
$jet login <username>


This command both logs you into Jet, and lets you sync your files with the servers at jetvc. Ensure you make an account on www.jetvc.co.uk/login/ before using!
$jet setup


A hook is a program to be run before the execution of a Jet command. This can be used to attach unit tests, checks or email alerts. You can attach hooks to either commits or pushes. By including the scripts name instead of inspect, you overwrite the previous script. The remove command simply removes the hook.
$jet hook <commit|push> inspect
$jet hook <commit|push> <script_name>
$jet hook <commit|push> remove


This command clones a repository from jetvc and initializes it in the current directory. To find your repo id and branch name, click "download" on the repositorys homepage.
$jet clone <repo_id> <branch_name>


This command takes a snapshot of the current repository and creates a "save" of it that can be restored.
$jet stash
$jet unstash


This command marks a file with conflicts as resolved. This will allow commits when all files are resolved. Use conflicts command to see which files need resolving.
$jet resolve <filename>