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

Optionally allow for additional "--out-format" support #612

Closed
2 tasks done
chainchad opened this issue Dec 2, 2022 · 1 comment · Fixed by smartcontractkit/chainlink#10024
Closed
2 tasks done
Labels
duplicate This issue or pull request already exists

Comments

@chainchad
Copy link

Welcome

  • Yes, I understand that the GitHub action repository is not the repository of golangci-lint itself.
  • Yes, I've searched similar issues on GitHub and didn't find any.

Your feature request related to a problem? Please describe.

I saw some issues where others were looking for similar functionality. I would like to use this action with SonarQube's GitHub Action, which requires a file uploaded for a lint report.

Describe the solution you'd like.

I understand that golangci-lint can support multiple --out-format's and that this action hardcodes --out-format=github-actions and prevents any additional --out-format args. However, I would like to keep the hardcoded default but then optionally override this prevention to support additional --out-format's so I can generate a file for use with the SonarQube action.

Describe alternatives you've considered.

One alternative would be to just remove the check which prevents any additional args with --out-format.

Additional context.

No response

@ldez ldez added the enhancement New feature or request label Jan 16, 2023
@ldez ldez added duplicate This issue or pull request already exists and removed enhancement New feature or request labels Jun 9, 2023
@ldez
Copy link
Member

ldez commented Jun 9, 2023

duplicate of #458

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants