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
This issue was migrated from Pagure Issue #703. Originally filed by kaskahn on 2013-08-09 18:40:01:
Closed at 2018-04-06 14:37:11 as fixed
Assigned to nobody
Currently pylint scans cause a build failure only if there are any errors or warnings in the code. All the conventions and refactoring issues are written to a file pylint-report in packages folder. It is required to investigate and fix these issues which improve the code. It can also be discussed if the build must fails if any of these types of issues show up.
The text was updated successfully, but these errors were encountered:
Currently all Python code is checked with pylint and flake8 via CI before commit. All remaining warnings that cannot be fixed right now are explicitly waived.
This issue was migrated from Pagure Issue #703. Originally filed by kaskahn on 2013-08-09 18:40:01:
Currently pylint scans cause a build failure only if there are any errors or warnings in the code. All the conventions and refactoring issues are written to a file pylint-report in packages folder. It is required to investigate and fix these issues which improve the code. It can also be discussed if the build must fails if any of these types of issues show up.
The text was updated successfully, but these errors were encountered: