I know that the [no test files] is because you don't have tests for your main package, which is what I do as well for my go projects, but for a user who doesn't know about go testing it might strike them as confusing. Might be worth explicitly specifying the modules to test, or omitting the first in the list generated with $(go list ./... | tail -n +2)