R1.2 · Repo basics: descriptions, topics, website links, Discussions, social preview cards

Aperta
#115 1 commento 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github
Ambito
devops

Direzione di ricerca

Start with the parent issue R1 and review this repository’s GitHub settings and existing public repo presentation. The issue names no code files or tests; its subtasks cover descriptions, topics, website links, Discussions, social preview cards, and a reusable launch checklist. Done means every public repo meets the listed acceptance criteria and the checklist is ready for future launches.

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

Descrizione

story

Part of epic R1 · Public repos that wow (linked as parent issue).

Story

As a developer finding a patch-it repo on GitHub or in a shared link, I want a clear description, topics, a website link and a preview card, so the repo looks finished before I open it.

Subtasks

  • Write one-line descriptions for each public repo (this one, the docs repo, and each repo that goes public later) in the shared wording: the layers, "the fix, not the alert"
  • Add topics (e.g. dependencies, breaking-changes, api-changes, sdk, ai-models, ci, automation, pull-requests)
  • Set the website link on each repo
  • Turn on Discussions with categories: Q&A, Ideas, Show and tell, Announcements
  • Make a social preview card per repo (1280×640, IBM Plex and brand tokens, Patchy; no gradients or glows)
  • Upload each card by hand in Settings → General → Social preview (GitHub has no API for it)
  • Write the steps down so the same is done for each repo the day it goes public

Acceptance criteria

  • Every public repo has a description, topics and a website link
  • Discussions is on with the four categories
  • A shared link to each public repo shows its own preview card, not the default one
  • No description names a version bot or says "better than"; none says API-only
  • A short checklist exists for repos that go public later
Lingua principale
Go
Stelle
0
Fork
0
Merge medio
2h 59m
PR unite (30g)
17

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 patch-it-dev/patch-it-plugins

Tutte le issue di patch-it-dev/patch-it-plugins

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.