James Brundage

They should be able to match an existing file structure.

On linux, one can have README.md and readme.md as two separate files. On Windows, this can prevent a module from installing.

Formatting in PowerShell has come a long way since you originally wrote this module. Let's shake off some dust and see what it can do. Also, let's improve documentation.

ugit should support `git config` (since it's already basically objects, and this would be quite useful) This should consist of: * [x] #265

Sparse checkouts are a great way to save time and bandwidth. ugit should support them. Using them correctly spans a few commands, so this will require a few steps: *...

ugit should support functions. It a function is named `git.$nameofcommand`, it should be considered a git function. All punctuation should be treated as spaces. If the git command line matches...

* [x] Continue to support object output from new scenarios * [x] Integrate ugit into more projects * [x] Hype ugit more

ugit should include a series of demo files walking thru common git scenarios from the perspective of a git newbie.