Systers, an AnitaB.org community
[Part 2 of 2] Check for only pylint errors and ignore warnings,refactor,convention and fatal class messages (Backend)
Intro
Pylint is a tool that checks for errors in Python code, tries to enforce a coding standard and looks for code smells. It can also look for certain type errors, it can recommend suggestions about how particular blocks can be refactored and can offer you details about the code's complexity.Travis CI is a hosted continuous integration service used to build and test software projects hosted at GitHub.The task requires you to modify pylint check in the Travis script to check for only errors in pylint and ignore warnings, refactor, convention and fatal messages.
Prerequisite:
- Fork and clone Mentorship-Backend
- Run the project.
- Complete the [Part 1 of 2] Pylint Check:Add pylint check in Travis file for Mentorship Backend
Steps:
- Modify the pylint check under the script section in travis.yml file to disable Refactor, Convention, Warning, Fatal class messages.
Resources:
- Learn more about travis
- Learn more about pylint
- Learn more about different coding styles like flake8, pep8, pylint
- If you need help or get lost, post a "New topic" in the quality-assurance-tasks stream.
Work Submission:
Create a pull request in Mentorship-Backend attached in pull request description.
Task tags
Students who completed this task
_daksha_, asawesome07