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

Additional required file (if not already installed)

The following file is shared among the centralized GitHub Actions, and only needs to be

installed once. If the file does not exist in the repo, it will be generated and included with

the PR. It will be skipped if previously installed.

• Additional config file (unless previously installed):
  • github-actions/workflow-configs/_data/label-directory.json

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

Configuration required

1. Review configurations in the files shown, and note especially the explanations in the files themselves:

   • github-actions/workflows/add-update-label-weekly.yml
     • Adjust cron schedule as needed for your project https://crontab.cronhub.io/
     • Update if: github.repository == 'hackforla/repo-name' at ⓶
     • Double-check the version in uses: hackforla/automate-the-org/add-update-label-weekly@v0 at ⓷
   • github-actions/workflow-configs/add-update-label-weekly-config.yml
     • Review timeframes:, projectBoard: column-status names, and the required: and ignored: labels.
     • Update <teamSlackChannel>
   • github-actions/workflow-configs/templates/add-update-instructions-template.md
     • We recommend keeping this version, but if needed edit using markdown syntax.
   • github-actions/workflow-configs/_data/label-directory.json
     • Make sure that your label-directory.json file maps these keys:
       • keys needed by automation:
         • statusUpdated --> "status: Updated" (confirm)
         • statusInactive1 --> "status: To Update !" (confirm)
         • statusInactive2 --> "status: 2 Weeks Inactive" (confirm)
       • key used in message template:
         • statusHelpWanted --> "status: Help Wanted" (confirm)
       • keys which tell the automation to skip the issue:
         • Unlike the other keys, add or remove as needed:
         • draft --> "draft"
         • er --> "er"
         • epic --> "epic"
         • dependency --> "Dependency"
         • complexity0 --> "Complexity: Prework"

2. Test in dry-run mode

   • Go to Actions tab → "Add Update Label Weekly"
   • 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

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

---

Auto-generated by Rollout Workflow to Project(s) 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 at ⓶ to your repo
  • Delete in its entirety the step named "Generate token from GitHub App"
  • Change the version number at ⓷ to @v0.5.3
  • 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 }}
  

• label-directory.json
  • Even though the id values refer back to the Website, you do not need to change these. The worst that will happen is that the automation will not apply the labels to your test issues.
  • However, you can use something like the following if you want to replace the id values from your repo:

  gh api repos/your-github/your-repo/labels --jq '.[] | select(.name=="Some Label") | .id'
  

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.

[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).