Kiln is great! The command line is great! Unfortunately, Kiln is not the command line. Or is it…

Kiln Extensions let you use commands within the Mercurial command line tool to jump directly to the relevant information in Kiln. Now, you have the power of Kiln at your fingertips! If we were to document how powerful your fingertips are, we might express it like this:


hg kiln [-p url] [-r rev|-a file|-f file|-c|-o|-s|-t|-n branchName|--logout]

Or, we might talk a bit about the options available to you:

Commands

annotate

This brings you to the annotation view of the specified file in Kiln. You can repeat this to figure out who you can blame for changes across multiple files:

hg kiln --annotate thisFile.js --annotate thatFile.js

changes

View the history of the repository by jumping to the DAG. This is the default option, so the two examples below do the same thing:

hg kiln --changes
hg kiln

file

View the file contents. Can be used to view multiple files.

hg kiln --file sekritPasswords.py
hg kiln --file fileOne.py --view fileTwo.py

filehistory

View the history for a given file. File history is presented in a DAG view, showing changesets where it was modified. This option can be repeated.

hg kiln --filehistory sekritPasswords.py
hg kiln --filehistory fileOne.py --view fileTwo.py

outgoing

View the repository’s “outgoing” tab.

hg kiln --outgoing

settings

View the repository’s “settings” tab.

hg kiln --settings

path

Show the changes for a given repository. Use the full URL.

hg kiln --path https://yoursite.kilnhg.com/Repositories/Groups/repository

rev

Show the specified changeset in Kiln. You can use both revision numbers and changeset IDs here.

hg kiln --rev 12
hg kiln --rev 255ff  (only part of the changeset ID is required)

targets

View the repository’s targets.

hg kiln --targets

new-branch

Create a new Kiln Branch as a child of the current repository. Takes the name of the new child branch to create.

hg kiln --new-branch repository-child