-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[codeql] Collect statistics weekly #193308
Conversation
Moves stats collection from after the analyze scan to a weekly cron.
buildkite test this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
stats: | ||
name: CodeQL statistics | ||
runs-on: ubuntu-latest | ||
if: github.repository == 'elastic/kibana' # Hack: Do not run on forks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to be explicit, this worked for stopping the LaunchDarkly action from running on forks.
if: github.repository == 'elastic/kibana' # Hack: Do not run on forks | |
if: github.event.repository.fork == false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to hold off for the moment, this is working and I expect it won't cover the "not fork but clone and pushed" edge case. Not that I expect that to be common, will circle back of there's issues.
Moves stats collection from after the analyze scan to a weekly cron.