11–20 of 29 posts
I was hoping this was a code review tool that allows you to modify the PR without making a commit-merge-push loop, which could have approved changes automagically pulled locally (for the loop). This would save a TON on small edits that many PRs require, including any additional comments that people might want to add to code that come up during PR...modern PRs is where context goes to die.
This is a serverside pre-PR hook for an analyzer, as I understand it. I was hoping this was a code review tool that allows you to modify the PR without making a commit-merge-push loop, which could have approved changes automagically pulled locally (for the loop). This would save a TON on small edits that many PRs require, including any additional comments that people might want to add to code that come up during PR..…
That said, for the convenience of developers, we're working on the ability to run the analysis and the fixes using our CLI. [1] This opens up doors to use the CLI and build IDE plugins in the near future.
Congrats! Any plans to add support for more languages?
Ruby is already in beta, stable release in the next 3-4 weeks. Next up is JavaScript. Rust, Java, and PHP are further down the line.
Earlier quoted context omitted.
Ruby is already in beta, stable release in the next 3-4 weeks. Next up is JavaScript. Rust, Java, and PHP are further down the line.
How does it compare to static analysis as rubocop actually does. Especially in who decides what anti-patterns are
The general categorization of anti-patterns is based on the consensus of the community around the language, and also some obvious things based on objective reasons. Although we understand that everyone has their own flavor of conventions — so it is very easy to triage and ignore specific issues in DeepSource.
When you offer support for C++, we'll talk. More challenging to parse and analyze, of course.
Quick question: I tried setting it up but its asking for Write access to the pull requests. I am a bit wary about giving write access - is this required?
This looks awesome - congrats on the launch. Quick question: I tried setting it up but its asking for Write access to the pull requests. I am a bit wary about giving write access - is this required?
By default, on signup, you would be installing the app with read access -- this enables us to pull source code from GitHub on every commit and pull-request, run analysis and report issues as GitHub checks. This is sufficient if you would like to use DeepSource only to flag issues.
With the release of Autofix -- when a fix is available for a flagged issue, DeepSource creates a pull request to the repository with the patch. For this, you would be asked to install the app with write access (DeepSource Autofix). Note that, DeepSource always creates a separate branch with the fixes and creates a pull request. We do not perform any write operations beyond the above mentioned scope.
Congrats on the HN launch guys :) Excited to see Javascript being added to the list of supported languages soon.