One page per verb

GitDepend does not correctly handle the case where no arguments are supplied to the program.

Update README.md to reflect work done in the v0.2.0 milestone

pull requests that are merged into release/v0.2 are resetting the build counter for gitversion.

Wrap the following git commands.

git checkout -b
git checkout

Unable to collect dependencies in the install folder when GitDepend was installed via an admin shell using choco install

The cache directory needs to be moved to a location that is not protected with admin privileges.

In one of my repositories, I'm getting a NullReferenceException right off the bat.

I would love to have a cool logo to use for branding purposes.

• An icon for nuget packages, gitter lobby, etc...
• A logo for the README page, and other supporting websites.

I'm not a graphics design person by any stretch of the imagination. I definitely need help here.

Clean up the home page of the docs

If you have switched a dependency repo to a new branch, and for whatever reason that branch is now out of sync with a consuming repo that specifies it needs a different branch, GitDepend will switch to the branch specified in the config file with no warning.

It would be nice to get some kind of warning saying "this is out of sync... what would you like to do?" etc...

The commit message made when consuming new dependency packages should include a description of which package id and version were taken during the update.

should be able to specify which dependency (or all dependencies)

This is a critical feature. Almost everything else in the product will need to use the information from GitDepend.yml. There needs to be a way to read in GitDepend.yml and represent the data as an in memory object.

The format of the file is as follows

build:
  script: make.bat
packages:
  dir: artifacts/NuGet/Debug
dependencies:
  LibA:
    url: ssh://[email protected]:kjjuno/liba.git
    dir: ../LibA
    branch: develop
  LibB:
    url: ssh://[email protected]:kjjuno/liba.git
    dir: ../LibB
    branch: develop

GitDepend.exe update should recursively run the build script for all dependencies, and update to the latest packages.

Use LibGit2Sharp instead

GitDepend.exe --init should help the user to create a GitDepend.json file

Adding new dependencies is getting ridiculous. We need to be using a dependency injection framework to make the construction of objects less tedious.

When GitDepend returns an error code it should display an english description of that error code

If possible use nuget.core or some other method for restoring and updating nuget packages.

Use github api to check releases

After building dependent repositories there should be new nuget packages that have been produced. These new nuget packages need to be referenced in the csproj and packages.config files.

This is similar to doing a nuget.exe update command, but we need to be able to specify the exact version to take for a specific package.

• If any nuget dependencies are removed or introduced those should also be reflected in the csproj and packages config files.

Gitdepend should be a stand alone exe without a bunch dlls required

Add a document meant for those who would like to contribute

After a GitDepend.exe update command it should print a summary of what just happened.

the update flag needs to make a new commit after consuming new dependencies. This will allow build systems relying on GitVersion to properly bump the version.

The chocolatey package currently makes a shim for GitDepende.exe => gdep. This should change to just dep

GitDepend.exe clone should recursively clone all repositories specified in GitDepend.json

GitDepend.exe update should recursively run the build script for all dependencies.

update currently updates all dependencies. There should be an option to only update a specific dependency.

make.bat should produce a chocolatey package for GetDepend

the sphinx docs are still pretty much empty. Those need to be updated to reflect how v0.2.0 works

It would be extra nice if this list would print a tree or a graph to visually show the dependency graph.