-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Run brakeman in GitHub Actions #23713
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
37c5ad8
to
11ba3d3
Compare
This comment was marked as outdated.
This comment was marked as outdated.
FYI I already removed CodeClimate from the repository so you can remove its configuration file. |
Thanks, I had dropped that one, but it created a bunch of issues, so I put it back in. |
49023a1
to
0b69ad4
Compare
@Gargron I deleted the config file again, but it looks like the application is still installed in the GitHub App Settings, since it's showing the failed hook results. |
ecaa890
to
17aba12
Compare
Because of the unrelated CI failure on #24019, I figured it was a better idea to split out the |
@Gargron is it easier if I restore the codeclimate file and just disable the last brakeman config? |
fad358d
to
7a292d9
Compare
oops, sorry I missed that, and I'm actually surprised we've stopped running brakeman… when did that happen? Is there a way we can have brakeman's results more prominent and readable, instead of having them buried in the Ruby Linting action logs? |
Maybe with something like https://github.com/reviewdog/action-brakeman ? |
This pull request has merge conflicts that must be resolved before it can be merged. |
Allows it to run on a cron schedule to see about new issues outside of a PR run
This pull request has resolved merge conflicts and is ready for review. |
When codeclimate was removed |
Try using GitHub
and CodeQLfor brakeman results