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

Aberta
#115 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github
Domínio
devops

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
Go
Estrelas
0
Forks
0
Merge médio
2h 59min
PRs com merge (30d)
17

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de patch-it-dev/patch-it-plugins

Todas as issues de patch-it-dev/patch-it-plugins

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.