Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Install workflow: Add Update Label Weekly

Aperta
  • Qualcosa non va?
#2,215 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@Tharunya07 ci sta già lavorando.

Dal 26/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

feature: Github Actions role: Product size: 0.25pt

There will be some changes needed when we install the automation that will do a weekly reminder and labeling on issues where people have left updates or not left updates, before it can be reviewed an accepted. Those changes will be made by me. Just adding my notes here for later

I tried to run this, but it has a token problem. I will fix for next week
https://github.com/hackforla/automate-the-org/actions/runs/33817832880

edit this file github-actions/workflows/add-update-label-weekly.yml

  • Adjust the cron schedule for our project

    • When do we want the reminder to run? Tuesday at 10:00 AM Pacific. cron: "0 17 * * 2"
    • 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"
Lingua principale
JavaScript
Stelle
61
Fork
103
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hackforla/VRMS

Tutte le issue di hackforla/VRMS

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.