Linthub: Static code analysis for GitHub pull requests
1–10 of 35 posts
Re: Linthub: Static code analysis for GitHub pull requests
#2Re: Linthub: Static code analysis for GitHub pull requests
#3This looks pretty awesome and will just get better as more languages get supported. But, it comments on commits, not on the diff in the PR. I think commeting on the diff looks nicer (you see code snippet with the comment) and in my opinion it's also easyer to find all the comments that way. Instead of clicking the commit hash on the commen each time.
Re: Linthub: Static code analysis for GitHub pull requests
#4What's your plan on this? I'd like to use it for our private repositories.
Edit: My web hooks are returning errors. I'll submit some feedback.
Re: Linthub: Static code analysis for GitHub pull requests
#5So this is like Hound[1]? - I am (kinda) building something for PHP, Anorak[2] which uses something else I built. What's your plan on this? I'd like to use it for our private repositories. Edit: My web hooks are returning errors. I'll submit some feedback. [1] https://houndci.com [2] https://github.com/jbrooksuk/anorak
Re: Linthub: Static code analysis for GitHub pull requests
#6So this is like Hound[1]? - I am (kinda) building something for PHP, Anorak[2] which uses something else I built. What's your plan on this? I'd like to use it for our private repositories. Edit: My web hooks are returning errors. I'll submit some feedback. [1] https://houndci.com [2] https://github.com/jbrooksuk/anorak
It seems comparable, though we are supporting different languages. Plans are to support a lot more languages, and support private repos also. (Actually they are already supported, but linthubot needs to have read only access to the repository). All feedback is welcome.
Edit: Nevermind, I found the support form.
Re: Linthub: Static code analysis for GitHub pull requests
#7Earlier quoted context omitted.
It seems comparable, though we are supporting different languages. Plans are to support a lot more languages, and support private repos also. (Actually they are already supported, but linthubot needs to have read only access to the repository). All feedback is welcome.
Thanks! Are you planning on charging for this? I have an error, can I email you guys? Edit: Nevermind, I found the support form.
Re: Linthub: Static code analysis for GitHub pull requests
#8Earlier quoted context omitted.
It seems comparable, though we are supporting different languages. Plans are to support a lot more languages, and support private repos also. (Actually they are already supported, but linthubot needs to have read only access to the repository). All feedback is welcome.
Thanks! Are you planning on charging for this? I have an error, can I email you guys? Edit: Nevermind, I found the support form.
Re: Linthub: Static code analysis for GitHub pull requests
#9If the code has coding style violations, the build breaks. Exactly like it would if we pushed a failing test.
Personally, I’m not a fan of the noise generated by comments about coding style on pull requests.
Re: Linthub: Static code analysis for GitHub pull requests
#10Instead of using a service like this one (or Hound) that comments directly on pull requests, we chose to integrate the same tools in our build process with Phare ( https://github.com/mirego/phare ), a command-line tool we built which runs Rubocop, JSHint, JSCS, etc. and exits with a global status. If the code has coding style violations, the build breaks. Exactly like it would if we pushed a failing test. Personally,…