Feature/scheduled runs

[zricethezav]

This PR adds a feature that allows users to enable "scheduled" scans.

Related issue: #77

Note that in order for "schedule" GitHub-Actions jobs to run the workflow must be present on the default branch. You can see this in our private fork.

Also note that the event json GitHub provides is pretty sparse. This is the reason why most of the changes in this PR revolve around filling the even json so that we can use it in other parts of the code.

[zricethezav]

@weineran mind giving this a review?

[weineran]

Oh great!

…

On Sun, Sep 11, 2022, 3:55 PM Zachary Rice ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In src/index.js <#89 (comment)> : > // Examples of event types: "workflow_dispatch", "push", "pull_request", etc const eventType = process.env.GITHUB_EVENT_NAME; // Determine if the github user is an individual or an organization -const githubUsername = eventJSON.repository.owner.login; +let githubUsername = ""; + +// eventJSON.repository is undefined for scheduled events +if (eventType == "schedule") { + githubUsername = process.env.GITHUB_REPOSITORY_OWNER; @weineran <https://github.com/weineran> Does this mean the user would have to set GITHUB_REPOSITORY_OWNER and GITHUB_REPOSITORY in their yaml file? Or are those env variables automatically set by GitHub? The env vars are automatically set by GitHub. Source: https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables The default environment variables that GitHub sets are available to every step in a workflow. — Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNAEIKV3QQKDBXMEOJVG4LV5ZPPLANCNFSM6AAAAAAQI2J7WM> . You are receiving this because you were mentioned.Message ID: ***@***.***>