I would like to have 2 repositories in the future, so that pgn-reader and pgn-viewer may be more independent developed. Most people using the current implementation use the npm install way, so splitting is not a danger for them.
Do the following:
Read what is documented about a split of repository. (see Renaming a repository how to do that)
Think what will be the effect on Github pages (documentation and configuration builder).
Do I need the history of pgn-reader (separated from the viewer). I doubt that ...
Then decide in which steps the migration should be done. Something like:
✔ Move out the reader part (perhaps by cloning to keep the history, then moving the directories).
✔ Restructure the existing repo: move the directories over, remove unneeded generalization.
✔ Create a new build that is then deployed to Github Pages, under a new URL.
✔ Correct all documentation to reflect the new URL (hopefully not too much).
I would like to have 2 repositories in the future, so that pgn-reader and pgn-viewer may be more independent developed. Most people using the current implementation use the
npm install
way, so splitting is not a danger for them.Do the following:
Then decide in which steps the migration should be done. Something like: