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

community: enable Discussions, auto-label and welcome external PRs, and state a response time

Aperta
  • Qualcosa non va?
#119 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, github-actions, javascript
Ambito
developer-experience, devops

Direzione di ricerca

Start with CONTRIBUTING.md and inspect the repository’s existing GitHub Actions workflows and settings; the issue names labeler.yml and CODEOWNERS as proposed additions. Check how first time contributors’ PRs are approved and how the catalog, site, and docs paths are organized. Done means Discussions is enabled, new PRs receive path based labels and a welcome comment, and CONTRIBUTING states the review window.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

community priority: medium

Why it matters
External contributions are arriving (PRs #48, #52, #78 from three people) but the path is bumpy: PR #78 has been open since 2026-10-16 with no review and no "Validate catalog" run, because first-time-contributor workflows wait for manual approval. Questions ("is this licence OK for…") have nowhere to go but issues, and there is no Discussions tab.

Evidence

  • gh pr view 78: open since 2026-10-16, no review, checks show only Socket Security; the validate run is in action_required.
  • gh api repos/TMHSDigital/Free-Game-Dev-Assets → has_discussions: false.
  • CONTRIBUTING.md says what to do but not what to expect.

Suggested approach

  1. Enable Discussions with Q&A, Asset requests and Show and tell (games shipped with catalog assets double as marketing).
  2. A labeler.yml workflow labelling PRs by path (catalog/** → new-source/correction, site/** → site, docs/** → documentation) and a first-PR welcome comment that explains the approval step and links the checklist.
  3. Review the Actions setting for first-time contributors, or document why approval is needed.
  4. A sentence in CONTRIBUTING on the review window and a CODEOWNERS file so review requests are automatic.

Done when
Discussions is on, new PRs get labels and a welcome comment automatically, and CONTRIBUTING states the expectation.

Lingua principale
JavaScript
Stelle
58
Fork
15
Merge medio
16h 53m
PR unite (30g)
14

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 TMHSDigital/Free-Game-Dev-Assets

Tutte le issue di TMHSDigital/Free-Game-Dev-Assets

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.