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

Offen
#115 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github
Bereich
devops

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
Go
Sterne
0
Forks
0
Ø Merge
2 Std. 59 Min.
Gemergte PRs (30 T.)
17

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus patch-it-dev/patch-it-plugins

Alle Issues in patch-it-dev/patch-it-plugins

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.