Open dhruvkb opened 11 months ago
Hi @dhruvkb, I can work on this!
Sure, please do! I'll assign this issue to you.
Is .github/workflows/weekly_updates.yml not already running a github action based job?
It's currently invoked as a Node.js script. This means that to run this, we first need to set up up Node.js, install dependencies and then finally invoke the script using a run
step.
We want to update the script so that we can invoke it from actions/github-script
. This generally involves
main()
functiongithub
argumentcore
argument and then using core.info()
, core.warn()
and core.error()
for loggingFor an example, see the issue_automations.yml
workflow. It does not need a setup step and we get access to an authenticated Octokit instance (octokit
) and the GitHub actions toolkit (core
) for free.
You can also refer to the actual script automations/js/src/project_automation/issues.mjs
that contains the aforementioned main()
function.
Hi @danielbmasud, I've unassigned you from this issue. If you would like to work on it again in the future please let us know. Thanks!
Description
The weekly update script
last_week_tonight.mjs
runs as a standalone Node.js script. It is the last remaining standalone script in the JS based automations. Converting it to aactions/github-script
based job would bring the following improvements:@octokit/rest
to a dev-dependencyThis is closely related to #3445 as they both deal with improvements to the same workflow.