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

未关闭
#115 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github
领域
devops

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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
主要语言
Go
星标
0
派生
0
平均合并
2 小时 59 分钟
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

patch-it-dev/patch-it-plugins 的其他 Issue

查看 patch-it-dev/patch-it-plugins 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。