Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Install workflow: Add Update Label Weekly

未关闭
  • 哪里不对？
#2,215 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Tharunya07 已经在做这个了。

开始于 2026年9月26日。

评估

这个 Issue 还没有评估数据。

描述

feature: Github Actions role: Product size: 0.25pt
Overview

We need to install a GitHub Action checks all issues in specific columns, adds "status" labels, and reminds team members if they need to do updates.

Details

There will be some changes needed when we install the automation. Those changes will be made by the PM team

Action Items

Figure out answers to the following:

  • Adjust the cron schedule for our project

    • When do we want the reminder to run?
    • use this if its helpful to determine new chron (https://crontab.cronhub.io/) but you could also use chatgpt

  • review and update "Time thresholds (in days)"

    • The timeframes: section defines placeholder keys that represent time thresholds, measured in days. Each issue’s update status is determined by comparing the assignee’s most recent activity timestamp against these defined thresholds.
    • Default values are provided and can be used as-is without modifications.

      • recentlyUpdatedByDays: Issues updated within this many days are considered current

      • needsUpdatingByDays: Issues not updated for this many days are prompted for update

      • isInactiveByDays: Issues not updated for this many days are marked as inactive

      • unassignedByDays: Issues not updated for this many days have assignees removed <-- FUTURE FEATURE

      • upperLimitDays: Bot comments older than this not processed for minimization <-- see below

      • current values

        recentlyUpdatedByDays: 3
        needsUpdatingByDays: 7
        isInactiveByDays: 14
        unassignedByDays: 21
        upperLimitDays: 35

      • value I am changing

          needsUpdatingByDays: 6
        • reason 
          I want it to apply the `To update!` label if they have not done an update anytime after the meeting on Wednesday but before the time the script runs on Tuesday.

  • Potentially Update the name of the question column to our vrms column header name

    • What is the name of our Question column on the board : "Questions/Review" targetStatus: "In progress"
    • "Project Board status-column configuration"
      • The projectBoard: section defines placeholder keys representing Project Board status-column names. Similar to the required labels, each placeholder status-column key must map exactly to a status-column on your Project Board.
        Change the values as needed for an exact match, and ensure the status-column value is in double quotes.

  • Update the script default Slack channel to "vrms"

    • "Bot comment template"
      • For the optional variable teamSlackChannel: Add your team's Slack Channel (once again in "double quotes") if you want this info on the Bot comment template.

  • find label names and see if they need to be changed or created ---added the exact labels, have not updated it with any issues yet. will do after successful dry run

    • Required label(s)

      Key value
      (Do not change)      		 Default value
      (in config file)
      statusUpdated: "status: updated"
      statusInactive1: "status: to update!"
      statusInactive2: "status: 2 weeks inactive"
      statusHelpWanted: "status: help wanted"

    • Filtering label(s)

      Key value
      (N/A)      		 Default value
      (in config file)
      --- "draft"
      --- "er"
      --- "epic"
      --- "dependency"

    **filtering:

    • "draft"
    • "Epic/Overview"
    • "Dependency - Icebox"**

  • find column names and see if they need to be changed or created -- be changed to vrms value: "In progress" and "Questions/Review"

    • Project Board status-columns
      Key value
      (Do not change)      		 Default value
      (value in config file)
      targetStatus: "In progress (actively working)"
      questionsStatus: "Questions / In Review"
Resources/Instructions
  • edit this file github-actions/workflows/add-update-label-weekly.yml
    • Chron will be set for: Saturay at either 12:07 or 1:07 depending on daylight savings time this is in UTC: The R 7 8 * * 6
主要语言
JavaScript
星标
61
派生
103
平均合并
14 分钟
30 天内合并 PR
1

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

hackforla/VRMS 的其他 Issue

查看 hackforla/VRMS 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。