Delete the four orphaned files left behind by the old label automation #220

Overview

We need to delete four files under github-actions/ that nothing references any more, because the 2024 workflow that used them was replaced in #213 by the Automate-the-ORG version, which brings its own logic from hackforla/automate-the-org. Leaving them behind makes the repo look like it still owns label automation that it does not.

Action Items

• Delete these four files:
  - github-actions/trigger-schedule/add-update-label-weekly/add-label.js
  - github-actions/trigger-schedule/add-update-label-weekly/update-instructions-template.md
  - github-actions/utils/find-linked-issue.js
  - github-actions/utils/get-timeline.js
• Expect two directories to disappear entirely as a result — github-actions/trigger-schedule/, whose only child is add-update-label-weekly/, and github-actions/utils/, whose only contents are the two files above. That is correct, not an over-delete.
• Do not delete github-actions/workflow-configs/. It sits in the same parent directory and is actively read by the new Automate-the-ORG workflow. The trigger-schedule/ and utils/ subtrees are the dead ones.
• Before opening the PR, re-run the check that proved this is a closed set: grep the whole repo for add-label, find-linked-issue, get-timeline and update-instructions-template, and confirm the only matches are the files being deleted. add-label.js is the only thing that requires the two utils/ modules, so deleting it alone would strand them — all four go or none do.
• After the PR merges, confirm add-update-label-weekly.yml still runs. Trigger it from the Actions tab (it has workflow_dispatch) and check the run completes. None of the deleted files is on its path, so this is a regression check rather than an expected failure point.

Resources/Instructions

• The workflow that used to read these files was replaced in #213; the logic now lives in hackforla/automate-the-org.
• All four files were confirmed still present on master on 2026-09-07, along with the directory contents described above. Paths are accurate as of that date.
• Deliberately out of scope, raise separately rather than blocking on it: the old workflow read an IN_PROGRESS_COLUMN_ID value that nothing reads now. It is not a devops repo secret — this repo has none — so it is either an org secret or already gone, and confirming needs admin:org.