-
Notifications
You must be signed in to change notification settings - Fork 46
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
create GitHub workflow #686
Comments
Hello David, could you please clarify the motivation and value? In its current state, you can download the binaries or build the tool yourself simply by using |
Thanks for let me know. Knowing that Google has its internal CICD framework, a public user has no test coverage visibility on this project, especially since data migration, the serious topics, mandates strict constraint on the tool we select. And only the visible capacities covered by tests are considered reliable. |
I agree with your motivation, we have the test coverage report in the following path |
If we really confirm that this coverage report IS the presentation layer for reader, that it should be included in the git history. Otherwise, release it to a seperate webpage. But now it is 404. Getting it by build from source is clumsy. |
I want it to cover more general install cases
The text was updated successfully, but these errors were encountered: