-
-
Notifications
You must be signed in to change notification settings - Fork 859
Bug fix and clean up of "Schedule Monthly" workflow #8596
Copy link
Copy link
Open
Labels
Complexity: LargeFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 5ptCan be done in 19-30 hoursCan be done in 19-30 hours
Metadata
Metadata
Assignees
Labels
Complexity: LargeFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 5ptCan be done in 19-30 hoursCan be done in 19-30 hours
Type
Projects
Status
In progress (actively working)
Overview
We need to address minor code errors in "Schedule Monthly" that caused unintended results in the December run so that our workflows run as expected.
Details
The 12/1/25 run of the "Schedule Monthly" workflow did not work as expected in two areas:
await.create-new-issue.js, the created objectconst issue = await createIssue(owner, repo, inactiveLists);includes the URL for the issue. We can return this URL and use it inwr-schedule-monthly.ymldirectly, skipping the steps "Get owner url" and "Get issue number" in the job "Close new issue". The benefit is that we are ensured of having the correct issue number.letvariable declaration should beconst.non-PR contributionlabel to so this issue is not reopened.Action Items
In trim-inactive-members.js:
awaittoclosePrework(username, inactiveWithOpenSkills[username]);- this function isasync.fs.writeFile()tofs.writeFileSync().In create-new-issue.js :
return issue.html_urltomain()In wr-schedule-monthly.yml:
non-PR contributionResources/Instructions