Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Consider converting react-seed into a template

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

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
github

调研方向

Issue 中没有指出源文件或测试。首先检查仓库的 GitHub template-repository 设置和 seed 的入门指南;当用户可以从中创建一个具有空历史记录且可选择公开或私有可见性的新仓库时,即视为完成。

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

描述

People who want to get started in building PatternFly UIs are encouraged to fork this seed repository as a starting point for their development, however repository forking was not intended for this purpose and thus doing it this way creates some annoyances for downstream developers:

  • The new repository can only be public because the source being forked is public

  • There is an existing git commit history that is not relevant to the project being developed

This means that users who want to bypass this will most likely simply clone the repository and push into a new one which is annoying/time consuming.

GitHub provides a feature known as template repositories [1] which makes these annoyances moot, users who create new repositories off of a template will start with a blank git commit history and are free to choose between public and private visibility for the generated repository.

[1] https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository


Jira Issue: PF-2031

主要语言
TypeScript
星标
97
派生
282
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

patternfly/patternfly-react-seed 的其他 Issue

查看 patternfly/patternfly-react-seed 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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