Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Install workflow: Add Update Label Weekly

Abierto
  • ¿Algo no está bien?
#2,215 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 4 días

@Tharunya07 ya está trabajando en esto.

Desde el 26/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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
Lenguaje dominante
JavaScript
Estrellas
62
Forks
106
Merge medio
3 d 19 h
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de hackforla/VRMS

Todos los issues de hackforla/VRMS

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.