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

Modify CVE Scan Schedule #286

Open
ystxn opened this issue Feb 13, 2024 · 1 comment
Open

Modify CVE Scan Schedule #286

ystxn opened this issue Feb 13, 2024 · 1 comment

Comments

@ystxn
Copy link
Member

ystxn commented Feb 13, 2024

Support Question

@yinan-symphony can you help make a modification to the CVE Scan GitHub Action so that GitHub will recognise you as the scan owner? I am still getting failure notifications because I was the last editor of that file. Strange way that GitHub implements notification owners.

https://github.com/finos/symphony-wdk/blob/master/.github/workflows/cve-scanning-gradle.yml#L5

https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs

Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead. If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.

@yinan-symphony
Copy link
Contributor

@ystxn yes, i will update it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants