This file records the agreed migration schedule so future sessions have local context.
- Keep the canonical GitHub repository at
https://github.com/jbeard4/scion. - Do not transfer the repository to the
SCION-SCXMLorganization for now.
The contents of projects/vendor/* are forks of third-party projects. Their
full upstream histories should not pollute the cleaned SCION repository history.
Use GitHub forks to preserve provenance, then keep SCION clean of vendored source.
Vendor fork mapping:
projects/vendor/eslint->https://github.com/jbeard4/eslintprojects/vendor/jsondiffpatch->https://github.com/jbeard4/jsondiffpatchprojects/vendor/react-codemirror->https://github.com/jbeard4/react-codemirrorprojects/vendor/react-collapsible->https://github.com/jbeard4/react-collapsibleprojects/vendor/sax-js->https://github.com/jbeard4/sax-jsprojects/vendor/vm-browserify->https://github.com/jbeard4/vm-browserifyprojects/vendor/xmllint->https://github.com/jbeard4/xml.js
For each vendored project, extract the SCION-side history for its vendor
directory and push that extracted history to a long-lived scion branch on the
corresponding fork.
- Create a backup branch from the current pre-rewrite state.
- Push the backup branch to
jbeard4/scionbefore any destructive rewrite. - Clone all vendor forks into
~/workspace/scion-vendor/. - Extract history from each
projects/vendor/<name>directory usinggit subtree split --prefix=projects/vendor/<name>. - Push each extracted history to the matching fork as branch
scion. - Replace SCION's local
projects/vendor/*dependencies with clean dependency sources, such as fork branches, package dependencies, subtree imports, or published packages. - Ensure the repository still builds and tests pass locally before rewriting history.
- Rewrite SCION history to remove
projects/vendor/, preferably withgit filter-repo --invert-paths --path projects/vendor/. - Re-run build and tests on the rewritten history.
- Force-push the cleaned
masterbranch tojbeard4/scion. - Add a "Fork me on GitHub" banner to sciblog pointing to
https://github.com/jbeard4/scion. - Add GitHub Actions test automation.
- Publish sciblog with Netlify or GitHub Pages.
- Prefer
git filter-repoovergit filter-branch. - Do not perform the history rewrite until the backup branch and all vendor
scionbranches are pushed and verified. - Treat force-pushing
masteras a migration event. Existing checkouts will need to reclone or manually reset. - Keep
spec/LOGand other explicitly local planning files untracked.