Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: mechanism to prune subtree #5018

Closed
robpike opened this issue Mar 9, 2013 · 2 comments
Closed

cmd/go: mechanism to prune subtree #5018

robpike opened this issue Mar 9, 2013 · 2 comments

Comments

@robpike
Copy link
Contributor

robpike commented Mar 9, 2013

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.
@adg
Copy link
Contributor

adg commented Mar 11, 2013

Comment 1:

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.

@robpike
Copy link
Contributor Author

robpike commented Mar 11, 2013

Comment 2:

Status changed to WorkingAsIntended.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants