From 153e5b6961c58f4145720ab31f438b25e81f2f00 Mon Sep 17 00:00:00 2001 From: Will Gillis <40799239+t-will-gillis@users.noreply.github.com> Date: Thu, 6 Nov 2025 09:24:14 -0800 Subject: [PATCH 1/4] Delete .github/workflow-configs/add-update-label-weekly-config.yml Testing completed, revert files from PR 8396 --- .../add-update-label-weekly-config.yml | 162 ------------------ 1 file changed, 162 deletions(-) delete mode 100644 .github/workflow-configs/add-update-label-weekly-config.yml diff --git a/.github/workflow-configs/add-update-label-weekly-config.yml b/.github/workflow-configs/add-update-label-weekly-config.yml deleted file mode 100644 index 4e7c70e9e5..0000000000 --- a/.github/workflow-configs/add-update-label-weekly-config.yml +++ /dev/null @@ -1,162 +0,0 @@ -# Configuration for "Add Update Label Weekly" action -# Copy this file to your project: `.github/workflow-configs/add-update-label-weekly-config.yml` -# -# ============================================================================== -# IMPORTANT NOTES -# ============================================================================== -# -# 1. The configuration options are given as "key: value" pairs. -# a. Do not edit any "keys" as this may break the automation. -# b. Customize the "values" below for your project's needs. -# 2. The default values will apply if not edited. -# 3. Text values must match the EXACT text used in your project repo. -# - - - -# ============================================================================== -# Time thresholds (in days) -# ============================================================================== -timeframes: - - updatedByDays: 3 # Issues updated within this many days are considered current - commentByDays: 7 # Issues not updated for this many days are prompted for update - inactiveByDays: 14 # Issues not updated for this many days are marked as inactive - - upperLimitDays: 35 # See explanation following and "Bot configuration" below - # To reduce issue clutter, this workflow includes a GraphQL mutation that iterates - # through and minimizes previous bot comments. To avoid GitHub's rate limiting - # on GraphQL mutations, bot comments older than the `upperLimitDays` are not - # minimized. A low value results in no bot comments minimized, and a high value - # results in all bot comments minimized. - - - -# ============================================================================== -# Project Board status-column configuration -# ============================================================================== -projectBoard: - # The values in this section must match your EXACT Project Board status-column. - - targetStatus: "In progress (actively working)" # Status-column to include. - # Only issues status-column are included in the automation to check whether - # assignees are updating their issues. - - questionsStatus: "Questions / In Review" # Used with the message template. - # The bot's message instructs issue assignees needing help to move their issue to - # this status-column. Issues in this status-column are NOT checked by the automation. - - - -# ============================================================================== -# Label Directory -# ============================================================================== - -# The automation reviews which labels have been applied to the included issues, to: -# 1. Flag issues that need updates from the assignee, and -# 2. Ignore issues that do not need to be checked. -# -# The workflow relies on the label "keys" to identify the purpose of each label -# which correspond to the actual label name "values" used by your repo. -# -# NOTE: Since different workflows use many of the same label names, label name -# values are mapped in your project's label directory yml file- not here. -# The path to your label directory is: - -labelDirectoryPath: ".github/workflow-configs/label-directory.yml" # Do not change - - - -# ============================================================================== -# Label keys used by this workflow -# ============================================================================== - -# The label "keys" shown here are used internally by the workflow. - -labels: - required: - # Required label keys: DO NOT REMOVE, confirm "values" in the label-directory - # The following label "keys" must be mapped to your project's actual label names - # "values" via the `label-directory.yml` file. The workflow using these labels - # to flag which issues need updates. - - statusUpdated # Map in the `label-directory.yml` file - - statusInactive1 # Map in the `label-directory.yml` file - - statusInactive2 # Map in the `label-directory.yml` file - - # Secondary key, used by message template - - statusHelpWanted # Map in the `label-directory.yml` file - - ignored: - # Issues with these labels are ignored by the automation. - # You may add or remove label "keys" to this list as desired- but be sure - # to map the added "key: value" pair in your label-directory.yml file. - - draft # Map in the `label-directory.yml` file - - er # Map in the `label-directory.yml` file - - epic # Map in the `label-directory.yml` file - - dependency # Map in the `label-directory.yml` file - - complexity0 # Map in the `label-directory.yml` file - - - -# ============================================================================== -# Bot configuration- If needed -# ============================================================================== -# Relevant to "timeframes.upperLimitDays" setting above. -# Bot usernames whose comments should be minimized when they become outdated. -# Comments are minimized if they're between 'commentByDays' and 'upperLimitDays' old -bots: - - "github-actions[bot]" - - "HackforLABot" - # Only if needed, add any additional bot usernames here - - - -# ============================================================================== -# Bot comment template -# ============================================================================== -# Template for the comment posted to issues needing updates -# Variables used by template: -# ${assignees} - @-mentions of all assignees (e.g., "@user1, @user2") -# ${label} - The label being applied (e.g., "Status: To Update") -# ${statusUpdated} - The "updated" label name from your label directory -# ${statusHelpWanted} - The "help wanted" label name from your label directory -# ${questionsStatus} - The "questions" status on your Project Board (e.g., "Questions / In Review") -# ${teamSlackChannel} - The name of your team's Slack Channel -# ${cutoffTime} - The formatted timestamp of the issue's last update -# -# You can use Markdown formatting to edit the template found at: - -botCommentTemplatePath: ".github/workflow-configs/templates/add-update-instructions-template.md" # Do not change - -# commentTemplate: | -# Hello ${assignees}! - -# Please add an update comment using the below template (even if you have a pull request). Afterwards, remove -# the `${label}` label and add the `${statusUpdated}` label. - -# 1. Progress: "What is the current status of your issue? What have you completed and what is left to do?" -# 2. Blockers: "Explain any difficulties or errors encountered." -# 3. Availability: "How much time will you have this week to work on this issue?" -# 4. ETA: "When do you expect this issue to be completed?" -# 5. Pictures (optional): "Add any pictures of the visual changes made to the site so far." - -# If you need help, be sure to either: 1) place your issue in the "${questionsStatus}" status column of the -# Project Board and ask for help at your next meeting; 2) put a `${statusHelpWanted}` label on your issue -# and pull request; or 3) put up a request for assistance on the team's Slack channel. - -# Please note that including your questions in the issue comments- along with screenshots, if applicable- -# will help us to help you. [Here](https://github.com/hackforla/website/issues/1619#issuecomment-897315561) and [here](https://github.com/hackforla/website/issues/1908#issuecomment-877908152) are examples of well-formed questions. - -# You are receiving this comment because your last comment was before ${cutoffTime}. - -# Thanks for being part of HfLA! - - - -# ============================================================================== -# Advanced options -# ============================================================================== -# Uncomment and configure these if needed for your project - -# # Custom timezone for cutoffTime display in comments (default: America/Los_Angeles) -# timezone: "America/New_York" From 8ba37916b077f1a686c005eecb2889c35a2d785a Mon Sep 17 00:00:00 2001 From: Will Gillis <40799239+t-will-gillis@users.noreply.github.com> Date: Thu, 6 Nov 2025 09:24:30 -0800 Subject: [PATCH 2/4] Delete .github/workflow-configs/label-directory.yml Testing completed, revert files from PR 8396 --- .github/workflow-configs/label-directory.yml | 85 -------------------- 1 file changed, 85 deletions(-) delete mode 100644 .github/workflow-configs/label-directory.yml diff --git a/.github/workflow-configs/label-directory.yml b/.github/workflow-configs/label-directory.yml deleted file mode 100644 index 79859b01c2..0000000000 --- a/.github/workflow-configs/label-directory.yml +++ /dev/null @@ -1,85 +0,0 @@ -# ============================================================================== -# Label Directory -# ============================================================================== -# -# If this file does not already exist in your repo, copy this example file -# to `.github/workflow-configs/label-directory.yml`. If you have copied this -# file previously, continue editing your existing `label-directory.yml` file. -# -# This file maps label "keys" (left) used internally by the workflow to the -# actual label names "values" used in your GitHub repository (right side): -# -# labelKey: "Actual Label Name in GitHub" -# -# Do not edit the label keys. Do, however, edit the label names to match the -# labels you are using in your project, especially any required labels noted -# in the `add-update-label-config.yml` file. -# -# When you implement additional workflows in the future, continue editing this -# same file for any additional labels noted in those workflows. -# -# ============================================================================== -# How to customize this file -# ============================================================================== - -# 1. DO NOT CHANGE the label "keys" on the left side - these are used internally -# by the workflow code -# -# 2. You can change the label name "values" on the right to match your project's -# naming conventions. Make sure label names are an exact match to your repo's -# labels (including capitalization and spacing). -# -# 3. If you add new label "keys" to your config file, add them here too -# -# 4. Make sure label names exist in your GitHub repository before running the workflow -# -# 5. If you do not edit the name values, or if you do not include this label-directory, -# the automation will substitute default values. - - -complexity0: "Complexity: Prework" # ⓵ -complexity1: "good first issue" -complexity2: "Complexity: Small" -complexity3: "Complexity: Medium" -complexityMissing: "Complexity: Missing" -dependency: "Dependency" # ⓵ -draft: "Draft" # ⓵ -epic: "epic" # ⓵ -er: "ER" # ⓵ -featureAdministrative: "Feature: Administrative" -featureAgenda: "feature: agenda" -featureAnalytics: "Feature: Analytics" -featureFeatureBranch: "Feature: Feature Branch" -featureMissing: "Feature Missing" -featureOnboardingContributingMd: "Feature: Onboarding/Contributing.md" -featureRefactorCss: "Feature: Refactor CSS" -featureRefactorGha: "Feature: Refactor GHA" -featureRefactorHtml: "Feature: Refactor HTML" -featureRefactorJsLiquid: "Feature: Refactor JS / Liquid" -readyForDevLead: "ready for dev lead" -readyForPrioritization: "Ready for Prioritization" -roleBackEndDevOps: "role: back end/devOps" -roleDesign: "role: design" -roleDevLeads: "role: dev leads" -roleFrontEnd: "role: front end" -roleMissing: "role missing" -roleUserResearch: "role: user research" -size025pt: "size: 0.25pt" -size05pt: "size: 0.5pt" -sizeMissing: "size: missing" -statusUpdated: "Status: Updated" # ⓵ -statusInactive1: "To Update !" # ⓵ -statusInactive2: "2 weeks inactive" # ⓵ -statusHelpWanted: "Status: Help Wanted" # ⓵ -skillsIssueCompleted: "Skills Issue Completed" - -# ============================================================================== -# Workflows using these labels -# ============================================================================== -# - ⓵ Add Update Label Weekly -# - ⓶ Issue Trigger -# - ⓷ PR Trigger -# - ⓸ Move Closed Issues -# - ⓹ Member Activity Trigger -# - ⓺ Schedule Monthly -# - ⓻ Update Label Directory From a618bd66d1bbc3b513ab682f2c31d9e7a4747fd1 Mon Sep 17 00:00:00 2001 From: Will Gillis <40799239+t-will-gillis@users.noreply.github.com> Date: Thu, 6 Nov 2025 09:25:11 -0800 Subject: [PATCH 3/4] Delete .github/workflow-configs/template/add-update-instructions-template.md Testing completed, revert files from PR 8396 --- .../add-update-instructions-template.md | 26 ------------------- 1 file changed, 26 deletions(-) delete mode 100644 .github/workflow-configs/template/add-update-instructions-template.md diff --git a/.github/workflow-configs/template/add-update-instructions-template.md b/.github/workflow-configs/template/add-update-instructions-template.md deleted file mode 100644 index 60c113b43e..0000000000 --- a/.github/workflow-configs/template/add-update-instructions-template.md +++ /dev/null @@ -1,26 +0,0 @@ - - - - - -Hello ${assignees} - -Please add an update using the below template (even if you have a pull request). Afterwards, remove -the `${label}` label and add the `${statusUpdated}` label. - -1. Progress: "What is the current status of this issue? What have you completed and what is left to do?" -2. Blockers: "Explain any difficulties or errors encountered." -3. Availability: "How much time will you have this week to work on this issue?" -4. ETA: "When do you expect this issue to be completed?" -5. Pictures (optional): "Add any pictures of the visual changes made to the site so far." - -If you need help, be sure to either: 1) place your issue in the "${questionsStatus}" status-column of the -Project Board and ask for help at your next meeting; 2) put a `${statusHelpWanted}` label on your issue -and pull request; or 3) put up a request for assistance on the team's Slack channel. - -Please note that including your questions in the issue comments- along with screenshots, if applicable- -will help us to help you. [Here](https://github.com/hackforla/website/issues/1619#issuecomment-897315561) and [here](https://github.com/hackforla/website/issues/1908#issuecomment-877908152) are examples of well-formed questions. - -Thanks for being part of HfLA! - -You are receiving this comment because your last update was before ${cutoffTime} PST. From e6ca1d883d7f76a4a3d3c63f279fbb1f753a53fb Mon Sep 17 00:00:00 2001 From: Will Gillis <40799239+t-will-gillis@users.noreply.github.com> Date: Thu, 6 Nov 2025 09:25:40 -0800 Subject: [PATCH 4/4] Delete .github/workflows/add-update-label-weekly.yml Testing completed, revert files from PR 8396 --- .github/workflows/add-update-label-weekly.yml | 41 ------------------- 1 file changed, 41 deletions(-) delete mode 100644 .github/workflows/add-update-label-weekly.yml diff --git a/.github/workflows/add-update-label-weekly.yml b/.github/workflows/add-update-label-weekly.yml deleted file mode 100644 index cf63cc5ce1..0000000000 --- a/.github/workflows/add-update-label-weekly.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: Add Update Label Weekly - -# Customization notes: -# ⓵ CUSTOMIZE: Change cron. Currently runs Fri 0700 UTC, exc. July and December -# ⮡ You can compose a schedule here: https://crontab.cronhub.io/ -# ⓶ CUSTOMIZE: Change to your project repo name -# ⓷ Confirm that this is the most recent version - -on: - schedule: - - cron: '0 7 * 1-6,8-11 5' # ⓵ - workflow_dispatch: - inputs: - dry-run: - description: 'Run in dry-run mode without posting comments or updating issues' - type: choice - options: - - 'true' - - 'false' - default: 'true' - -jobs: - Add-Update-Label-Weekly: - runs-on: ubuntu-latest - if: github.repository == 'hackforla/website' # ⓶ - steps: - - name: Generate token from GitHub App - id: generate-app-token - uses: actions/create-github-app-token@v1 - with: - app-id: ${{ secrets.HFLA_GRAPHQL_APP_ID }} - private-key: ${{ secrets.HFLA_GRAPHQL_APP_PRIVATE_KEY }} - - - name: Checkout repo - uses: actions/checkout@v5 - - - name: Run workflow - uses: hackforla/automate-the-org/add-update-label-weekly@v0.2.0 # ⓷ - with: - github-token: ${{ steps.generate-app-token.outputs.token }} - dry-run: ${{ github.event.inputs.dry-run || 'true' }}