Keeping vendor tree in sync with master

Is there a “preferred” way to keep the spf13/hugo/vendor tree in sync?

$ echo $GOPATH
$ go get -u
$ cd $GOPATH/src/
$ go build
$ which govendor
$ cd $GOPATH/src/
$ ls -l vendor/
-rw-r--r-- 1 user group 11544 Nov 26 13:16 vendor.json
$ govendor sync
$ ls -l vendor/
total 24
drwxr-xr-x   6 user  group    204 Nov 26 13:40 .
drwxr-xr-x  34 user  group   1156 Nov 26 13:16 ..
drwxr-xr-x  27 user  group    918 Nov 26 13:40
drwxr-xr-x   3 user  group    102 Nov 26 13:40
drwxr-xr-x   3 user  group    102 Nov 26 13:40
-rw-r--r--   1 user  group  11544 Nov 26 13:40 vendor.json
$ go clean
$ go install
$ ls -l $(which hugo)
-rwxr-xr-x  1 user  group  16996060 Nov 26 13:43 ~/go/bin/hugo
$ hugo version
Hugo Static Site Generator v0.18-DEV BuildDate: 2016-11-26T13:43:51-06:00

This vendoring thing is fairly new to me, but as we do not commit the /vendor folder, I feel the simplest solution is to do a

govendor sync

Inside the Hugo directory.

I notice we haven’t committed any folders under

BTW (just to clarify), since commit #6e692f2, I see we’ve been committing the file, vendor.json, which lives in

And your question was?

[quote=“bep, post:4, topic:4670, full:true”]
And your question was?
[/quote]Thanks; since you ask—please have a look at:

(So…should I commit the change I’ve now generated in vendor.json, or not? Alternatively, have I done something wrong?)

No and No.