-
Notifications
You must be signed in to change notification settings - Fork 26
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
Introducing linters to ops-toolbelt builds #151
base: master
Are you sure you want to change the base?
Conversation
This PR proposes changes that would break the pipeline definition:
|
40e2a3d
to
2dc6198
Compare
This PR proposes changes that would break the pipeline definition:
|
2dc6198
to
176a749
Compare
This PR proposes changes that would break the pipeline definition:
|
176a749
to
685ea03
Compare
This PR proposes changes that would break the pipeline definition:
|
This PR proposes changes that would break the pipeline definition:
|
I've disabled B404, as it's just generated when you call `subprocess`. In addition - I've dissabled B603 as we rely on the problematic part for the analisys.
This PR proposes changes that would break the pipeline definition:
|
This PR proposes changes that would break the pipeline definition:
|
d432f9c
to
80bdc9a
Compare
This PR proposes changes that would break the pipeline definition:
|
80bdc9a
to
3824991
Compare
This PR proposes changes that would break the pipeline definition:
|
3824991
to
ef0db7d
Compare
The pipeline-definition has been fixed. |
What this PR does / why we need it:
PR introduces SAST linters:
bandit
for python codeshellcheck
for bash codeWhich issue(s) this PR fixes:
Fixes #149
Special notes for your reviewer:
On release build lint outputs are saved within the root of the repo, rest of the pipeline execute the linters but don't save the results.
Release note: