You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the go.talks repo, the builders do something like
go build code.google.com/p/go.talks/...
but there is much bogus and/or disorganized code in the tree holding the presentations.
It would be nice to have an official way to say, "leave this tree alone",
perhaps a file that goes in the root of the subtree to be ignored. (Not a dot file!)
I've been putting build tags in every file but it's tedious, error-prone, requires
constant maintenance, and only works by luck, really, due to an interaction of the
present tool's rules and build tag syntax. We need a better way that will work in other
versions of this situation.
The text was updated successfully, but these errors were encountered:
For the record, the builders run:
go get -d code.google.com/p/go.talks/...
go test code.google.com/p/go.talks/...
so the code need not build. Only code that has tests must build.
My opinion is that go.talks (and, soon, go.blog) content authors should be mindful that
their code will be run with "go test". If they want it tested, they should add valid
_test.go files.
The text was updated successfully, but these errors were encountered: