go - 我需要将 gopkg.lock 添加到 Git 吗？

Question

鉴于:

The manifest describes user intent, and the lock describes computed outputs. There's flexibility in manifests that isn't present in locks..., as the "branch": "master" constraint will match whatever revision master HAPPENS to be at right now, whereas the lock is nailed down to a specific revision.

This flexibility is important because it allows us to provide easy commands (e.g. dep ensure -update) that can manage an update process for you, within the constraints you specify, AND because it allows your project, when imported by someone else, to collaboratively specify the constraints for your own dependencies.

引用:https://github.com/golang/dep/blob/master/docs/FAQ.md

Answer 1

是的，为了确保可重现的构建。

There's flexibility in manifests that isn't present in locks..., as the "branch": "master" constraint will match whatever revision master HAPPENS to be at right now, whereas the lock is nailed down to a specific revision.

任何使用锁定文件克隆您的 Go 项目存储库的人都将获得依赖项的确切 SHA1。
您仍然可以随时更新该锁定文件，并对其更新内容进行版本控制。