Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use codeclimate output format instead of pep8 for ansible-lint #114

Closed
ssbarnea opened this issue May 19, 2021 · 1 comment
Closed

Use codeclimate output format instead of pep8 for ansible-lint #114

ssbarnea opened this issue May 19, 2021 · 1 comment
Assignees
@ssbarnea
Labels
feature New feature or request

Comments

@ssbarnea
Copy link
Member

The codeclimate output format is JSON and includes information that is not part of the brief pep8 format, like the multiline description of the error, which sometimes contains critical information about how to fix it.

We only need to swap our parser and call the linter with -f codeclimate instead of -p.
@ssbarnea ssbarnea added the feature New feature or request label May 19, 2021
@ssbarnea ssbarnea self-assigned this May 19, 2021
@webknjaz webknjaz added the new label Aug 16, 2021
@ssbarnea ssbarnea removed the new label Aug 23, 2021
@ssbarnea
Copy link
Member Author

Done on default branch

ssbarnea pushed a commit that referenced this issue Mar 15, 2024
@ganeshrn
changed default execution environment image (#114)
d4ea3cd 
*  Update default execution environment image
   from `quay.io/ansible/ansible-navigator-demo-ee:0.6.0`
   to `quay.io/ansible/ansible-devtools-demo-ee:v0.1.0`
@ssbarnea ssbarnea mentioned this issue Mar 15, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ssbarnea ssbarnea

Labels
feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ssbarnea @webknjaz