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

Abierto
#115 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github
Área
devops

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
2 h 59 min
PR fusionados (30 d)
17

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

Todos los issues de patch-it-dev/patch-it-plugins

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.