Build from repository

Just for the sake of context: I'm building a bit of a wrapper project around this that will handle auto-configuration of projects. My workflow, in general, is to

1. Do a clean checkout of the repo I'm currently working on
2. Create a branch to hold my feature/bug
3. Initialize the project (we use ant)
4. Watch for the directory for changes and rsync to a remote server (sometimes)
5. Do some configuration (vhosts) on that same remote server (sometimes)
6. Finish my work and commit, push.
7. Wait for testers to be done and then delete everything.

While the majority of that doesn't fit in with the philosophy of desk and is really specific to my workflow, the bit about checking out from a repository might be. I'm envisioning something like

$ desk build github.com/owner/repo [desk-name]

Where you would previously configure where you want the projects to live (like configuring where you want the deskfiles to live).

This would create some stub deskfile (desk-name.sh) and do the git clone in your project directory.

The biggest things that I'd see with this are:

1. Tying desk to a specific scm (git) or host (github) OR trying to generalize and really bloating the code
2. Requiring an additional template file that would need to live somewhere and have a reference
3. Requiring users to configure and create a project directory

Maybe not ideal as laid out here, but potentially could be hammered into something useful 😄 I'd like to hear your thoughts on this, @jamesob.

Review the proposed desk build github.com/owner/repo [desk-name] workflow and the existing project-directory configuration before choosing an approach. Done would require an agreed scope for repository checkout, deskfile creation, and configuration, since the issue leaves the Git/GitHub integration and template design unresolved.