Vendoring repos lacking .go.yaml

[trans]

Started a new Go project, and want to use Gin web framework. So I added a dependency to my .go.yaml file for github.com/gin-gonic/gin. I get an error when running goat deps:

No .go.yaml found in [..]/.goat/deps/src/github.com/gin-gonic/gin

And no files for Gin get vendored.

My first thought is that, even if their is no .go.yaml file, shouldn't it still vendor the project?

My second thought was to look at Gin, where I discovered it is using the godep tool. It has some similarities to goat, but still works off the go workspace. But I was thinking it might be possible to read the GoDeps/GoDeps.json file to get the dependencies.

[mediocregopher]

Hey @trans, I appreciate you're still using goat and would like to contribute. Unfortunately I've gone back to simply using the default go get setup with a GOPATH and all that, without using goat. That said, I'm not really maintaining goat anymore, I don't really have time to do it and it's not a tool that I use =/ If you'd like though, you can fork the project and I'll put a link to your fork on my README, if you're interested in being a maintainer. Thanks again for keeping up using the project and contributing, sorry I can't be more help :(

[trans]

No problem. I understand. I just forked the project to: https://github.com/openbohemians/goat and I will be happy to maintain -- I've looked at a number of other dependency managers and none quite work for me. But if possible, could I ask a favor of you? Could you still offer your feedback on issues when time permits? It can be difficult to effectively work on a project alone, and since you are the original author, your advice will be especially helpful.

[mediocregopher]

Updated the readme on this project :) Thanks for picking it up!

I'm down to provide whatever advice I can, just @ me in an issue and I'll see what I can do. I'll warn you though, I haven't thought about these problems in a long time, you're honestly more qualified than me at this point I'll bet. But I'll do my best :P

As for this specific issue, I believe you're right that it should still vendor the project, does gin do anything weird regarding go's builtin vendoring?