David Varela

Getting very close now. Here is an example of toggling between tracking a repo and tracking a path: ``` (demo) pkg> add https://github.com/00vareladavid/Unregistered.jl Updating git-repo `https://github.com/00vareladavid/Unregistered.jl` Updating registry at `~/.julia/registries/General`...

The way that this currently works is that, whenever we track a dependency by path or by repo, we add the source url to the `source` table in the project...

I will rebase this soon. Any feedback for this, even if high level?

The goal for this PR is to make the use of unregistered dependencies as seamless as possible. Relying on the presence of manifests has two problems: (1) people have to...

Yeah that is a pretty bad error message. It happens when the active manifest and the test manifest both have fixed nodes that disagree (for example the active manifest and...

Yeah, that would make sense. Probably better than erroring out

The current iteration includes a `git_revision` field which returns the branch. I would be in favor of adding something like `Pkg.dependencies("path/to/project")` in order to avoid `Pkg.activate` (I think Stefan mentioned...