patternfly / patternfly/patternfly-react-seed

Consider converting react-seed into a template

Open
#158 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
97
Forks
282
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are identified in the issue. Start by reviewing the repository's GitHub template-repository setting and the seed's onboarding guidance; done means users can create a new repository from it with a blank history and either public or private visibility.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
developer-experience
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.