You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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
The text was updated successfully, but these errors were encountered: