Closed TimPansino closed 1 month ago
Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
---|---|---|---|---|---|
❌ PYTHON | bandit | 15 | 1 | 8.06s | |
✅ PYTHON | black | 33 | 5 | 0 | 4.64s |
❌ PYTHON | flake8 | 33 | 2 | 2.27s | |
✅ PYTHON | isort | 33 | 6 | 0 | 0.34s |
❌ PYTHON | pylint | 33 | 71 | 14.52s |
See detailed report in MegaLinter reports
_Set VALIDATE_ALL_CODEBASE: true
in mega-linter.yml to validate all sources, not only the diff_
Attention: Patch coverage is 78.12500%
with 35 lines
in your changes missing coverage. Please review.
Please upload report for BASE (
develop-remove-python27@8c1a4b9
). Learn more about missing BASE report.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Made a mistake merging and squashed everything, so I dropped the commit and force merged an identical PR (#1220)
Overview
Review
The best way to view selections made based on merge conflicts:
origin
to have up to date commit references.develop-remove-python27
.origin/main
to have an up to date copy of any merge conflicts.origin/merge-main-develop-python27
to see what selections and edits were made for all the merge conflicts. a. This is easier to view in VSCode with GitLens Inspect than in a terminal.