Dmitri Shuralyov

Quick note, there are some factors to consider when making the comparison above. I use Travis CI to ensure basic functionality and need everything to be passing [95%+ of the...

Thanks for reporting. I'll take a look at why the original query didn't work. It looks like it should work and this is a bug.

It's not a small example, but the `@include` directive is used [here](https://github.com/shurcooL/issues/blob/08d8dadf8acb9c08d7cb23769f7df13238e35353/githubapi/githubapi.go#L245).

> Currently, when scanning a Pull Request, GopherCI will perform the scans on HEAD. But it'd be more correct to do the scans on the merged HEAD. This reminds me...

What you said makes sense as future direction and enhancements. But until #8 is resolved, couldn't the 3 individual tools simply be replaced by `megacheck`? Is there a reason that...

> What's the reason for wanting it? It's good for speed, is that what you're looking for? Or to close off the issue? Either is a good reason. I thought...

> Do you agree or disagree with this? Do you think there's value in keeping the existing behaviour, or do you think it should be swapped, considering the fact the...

I will say you should _consider_ what it would be like to de-emphasize which tool a warning came from in your UI. If you decide that it's a good idea,...

In the comment above, I said: > It might make sense to have higher level categories though. Like, it might not matter so much whether a check came from `vet`...

Thanks for reporting this. `graphql` shouldn't panic, and I will fix that. But I suspect I see what the issue is. You're not specifying the exact pointer type for the...