Workflow for contributing to a vendored package

[krasi-georgiev]

Hi

The vendored packages don't seem to carry the .git metadata from the upstream.

I was wondering workflow do you use when package has a bug and I fix it locally (inside the vednored folder) and want to make a pull request.

[carolynvs]

Personally I do this:

1. Delete the package from my vendor folder temporarily. I just leave the dep config files alone and don't run dep ensure for a bit.
2. Work on the package in my GOPATH so that it's picked up automatically by the go tools.
3. Once my fix is upstream, or I'm ready to vendor my fork, I tweak my manifest to either use the fork by running dep ensure, or update to the latest version upstream by running dep ensure -update X to repopulate my vendor.

Essentially I would recommend against ever working in your vendor directory since dep will overwrite any changes. It's too easy to lose work that way.

[ibrasho]

Closing this since we've updated the FAQs in #755 to include an answer to this question.