Install workflow: Add Update Label Weekly

[hfla-workflow-rollout]

DO NOT MERGE

Automated Workflow Setup

This PR adds the "Add Update Label Weekly" GitHub Actions workflow to your project.

Files installed by this PR

• Workflow file:
  • .github/workflows/add-update-label-weekly.yml
• Configuration files:
  • github-actions/workflow-configs/add-update-label-weekly-config.yml
  • github-actions/workflow-configs/templates/add-update-instructions-template.md

What this workflow does

• Monitors open, assigned issues with the default status "In progress (actively working)"
• Checks for recent update comments from assignees
• Posts reminders for devs to provide issue progress updates
• Labels issues that need to be checked on

Security

• Uses organization-managed, secure GitHub App with just-in-time token
• Starts in dry-run mode (safe testing)
• No project-specific tokens or secrets needed

How to use

1. Review configurations and make changes to the respective files attached to this PR:

   • github-actions/workflows/add-update-label-weekly.yml
     • Adjust the cron schedule as needed for your project (https://crontab.cronhub.io/).
     • Current cron is scheduled to run Fridays at 0700 UTC, every week except in July and December.
   • github-actions/workflow-configs/add-update-label-weekly-config.yml
     • Configure specific values where shown on the config YML, but do not edit the keys or change the formatting except as explicitly noted.
     • The labels section includes lists of label key values that represent actual repo labels:
       • The required: section shows label placeholder keys that are essential to the workflow. Each label key must be mapped to an actual label name used in your repo, but do not change the key itself.
       • The filtering: section includes keys to labels which, when added to an issue, tell the workflow to omit the issue from the update checks. In other words, an issue that is labeled with one of the 'filtering' labels will be ignored by the workflow. Match each label key shown with an actual label name. If you do not need a value, replace it with "".
       • Preliminary label names may be shown. Confirm that all label names shown here exist in your repo or change as needed.
     • Configure the values for timeframes: referring to the notes in this section.
     • Configure the projectBoard: column-status names. Similar to the labels section, confirm the default values shown or where needed change to match your Project Board. Do not delete or edit the keys themselves.
     • Configure any remaining values as needed.
   • github-actions/workflow-configs/templates/add-update-instructions-template.md
     • We recommend keeping this version. If needed, edit using markdown syntax.

2. Test in dry-run mode

   • Go to Actions tab → "Add Update Label Weekly - ATO"
   • Click "Run workflow" → Keep dry-run = true.
   • Review logs to see which issues would be flagged and whether this is what you expected.

3. Live mode

   • When you have set up the configurations, the automation will run at the next scheduled time.
   • You can also manually trigger with dry-run = false if needed.

---

Auto-generated by Rollout Workflow to Project workflow.

---

Notes to PR reviewers:

Before reviewing this PR, you will need to have a Project Board set up in your environment.
Make the following changes to these files:

• add-update-label-weekly.yml:
  • Change the github.repository to your repo
  • Delete in its entirety the step named "Generate token from GitHub App"
  • Change the version number to @v0
  • Note: the workflow should run with the other settings. If not, let me know- might only need to add you to the repo.
  • Replace the github-token with:

  github-token: ${{ secrets.HACKFORLA_GRAPHQL_TOKEN }}
  

Test logs for the DRY-RUN
Test logs for the primary run

---

Soon: Will also add a link to "Automate the ORG" for the PR release for "v1.0.0"...

[github-actions]

@hfla-workflow-rollout[bot], this Pull Request is not linked to a valid issue. Above, on the first line of your PR, please link the number of the issue that you worked on using the format of 'Fixes #' + issue number, for example: Fixes #9876

Note: Do not use the number of this PR.

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

---

From your project repository, check out a new branch and test the changes.

git checkout -b hackforla-automation/rollout-central-workflow gh-pages
git pull https://github.com/hackforla/website.git automation/rollout-central-workflow

[github-actions]

@hfla-workflow-rollout[bot], this Pull Request is not linked to a valid issue. Above, on the first line of your PR, please link the number of the issue that you worked on using the format of 'Fixes #' + issue number, for example: Fixes #9876

Note: Do not use the number of this PR.

[daras-cu]

@t-will-gillis I tested this in my repo and it seems to be working as intended. On the normal run it correctly added the 2 weeks inactive label to two of my issues and left comments. Then on the subsequent dry run it recognized that there were new comments and would have removed the label (in this case it was the automatically generated comments from the previous run, but in practice these would not be left by the assignee).

[github-actions]

@hfla-workflow-rollout[bot], this Pull Request is not linked to a valid issue. Above, on the first line of your PR, please link the number of the issue that you worked on using the format of 'Fixes #' + issue number, for example: Fixes #9876

Note: Do not use the number of this PR.

[t-will-gillis]

Did final review, going live