-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add Pylint GitHub Action #76
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See pr joseph784#2
fixes bug actions/starter-workflows#636
Co-authored-by: Jason Ngo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. So is this going to start working once it gets merged into master or do we need to set up an account or give something access to this repo?
Also wondering if it would be worth consolidating this into CircleCI so that we don't have to maintain two different CI services.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Avoid running pylint on unchanged files
Co-authored-by: Jason Ngo <[email protected]>
Co-authored-by: Jason Ngo <[email protected]>
Co-authored-by: Andrei Popescu <[email protected]>
Co-authored-by: Jason Ngo <[email protected]>
No setup is required, it should be good to go once it's in main
I think this would be easier just doing it this way, but we could consolidate it if you want |
No description provided.