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.

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

Group output per linter #2755

Closed
adamralph opened this issue Apr 10, 2022 · 5 comments · Fixed by #4961
Closed

Group output per linter #2755

adamralph opened this issue Apr 10, 2022 · 5 comments · Fixed by #4961
Assignees
Labels
enhancement New feature or request O: backlog 🤖 Backlog, stale ignores this label

Comments

@adamralph
Copy link
Contributor

adamralph commented Apr 10, 2022

Is your feature request related to a problem? Please describe.

The output from super-linter is enormous. It's difficult to navigate to the output from a specific linter.

Describe the solution you'd like

The output from each linter grouped. For example:

::group::ansible-lint
# ansible-lint output
::endgroup::
::group::cfn-lint
# cfn-lint output
::endgroup::
::group::arm-ttk
# arm-ttk output
::endgroup::

# and so on...

which renders in GitHub actions as collapsible sections, similar to:


ansible-lint # ansible-lint output
cfn-lint # cfn-lint output
arm-ttk # arm-ttk output

# and so on...


Describe alternatives you've considered
n/a

Additional context
n/a

@adamralph adamralph added the enhancement New feature or request label Apr 10, 2022
@bewuethr
Copy link
Contributor

Or maybe even Markdown job summaries 🤩

@nvuillam
Copy link
Contributor

I think you are looking for MegaLinter , which has separate log files for each linter output👼

@ssulei7
Copy link

ssulei7 commented May 24, 2022

@bewuethr Second that. I am currently working on a POC to see how this would look like practically.

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

If you're a maintainer, you can stop the bot to mark this issue as stale in the future by adding the O: backlog 🤖 label`.

@github-actions github-actions bot added the O: stale 🤖 Stale issue/pr label Jun 24, 2022
@github-actions github-actions bot closed this as completed Jul 8, 2022
@ferrarimarco ferrarimarco added O: backlog 🤖 Backlog, stale ignores this label and removed O: stale 🤖 Stale issue/pr labels Dec 1, 2023
@ferrarimarco ferrarimarco reopened this Dec 1, 2023
@ferrarimarco ferrarimarco self-assigned this Dec 9, 2023
@ferrarimarco
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request O: backlog 🤖 Backlog, stale ignores this label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants