You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran DeepSource analysis on my fork of this repository and found some code quality issues. Have a look at the issues caught in this repository by DeepSource here.
DeepSource is a code review automation tool that detects code quality issues and helps you to automatically fix some of them. You can use DeepSource to track test coverage, Detect problems in Dockerfiles, etc. in addition to detecting issues in code.
The PR #24 fixed some of the issues caught by DeepSource.
All the features of the DeepSource are mentioned here.
I'd suggest you integrate DeepSource since it is free for Open Source projects forever.
Integrating DeepSource to continuously analyze your repository:
Create .deepsource.toml configuration specific to this repo or use the configuration mentioned below which I used to run the analysis on the fork of this repo.
Thank you for following up. I have another solution using pylint/black that I have yet to integrate but plan to. I'm sure this service has a lot of features but I'm not interested at this time. Thank you once again.
I ran DeepSource analysis on my fork of this repository and found some code quality issues. Have a look at the issues caught in this repository by DeepSource here.
DeepSource is a code review automation tool that detects code quality issues and helps you to automatically fix some of them. You can use DeepSource to track test coverage, Detect problems in Dockerfiles, etc. in addition to detecting issues in code.
The PR #24 fixed some of the issues caught by DeepSource.
All the features of the DeepSource are mentioned here.
I'd suggest you integrate DeepSource since it is free for Open Source projects forever.
Integrating DeepSource to continuously analyze your repository:
.deepsource.toml
configuration specific to this repo or use the configuration mentioned below which I used to run the analysis on the fork of this repo.The text was updated successfully, but these errors were encountered: