Skip to content

Consider converting react-seed into a template #158

Open

Description

@Elkasitu

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

Activity

  1. moved this from Needs triage to Ready to assign in PatternFly Issueson Jun 23, 2023
  2. changed the title [-]Consider converting this repository into a template[/-] [+]Consider converting react-seed into a template[/+] on Jul 10, 2023
  3. moved this from Ready to assign to Backlog in PatternFly Issueson Apr 19, 2024
  4. added this to the Prioritized Backlog milestone on Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions