go - 提交 `vendor` 目录是最佳实践吗？

Question

我正在使用 dep 来处理我的 Go 依赖项。将 vendor 目录也提交到版本控制中是最佳做法吗？还是在 checkout 存储库后始终执行 dep ensure 的最佳做法是？

Answer 1

dep 工具的常见问题解答 answers这个:

Should I commit my vendor directory?

It's up to you:

Pros

• It's the only way to get truly reproducible builds, as it guards against upstream renames, deletes and commit history overwrites.
• You don't need an extra dep ensure step to sync vendor/ with Gopkg.lock after most operations, such as go get, cloning, getting latest, merging, etc.

Cons

• Your repo will be bigger, potentially a lot bigger, though prune can help minimize this problem.
• PR diffs will include changes for files under vendor/ when Gopkg.lock is modified, however files in vendor/ are hidden by default on GitHub.