Monorepo for personal projects. The goal is to reduce duplicated effort and make it easier to stay consistent between projects.
A template of this monorepo -- all the boilerplate and helper scripts but without my packages --
is extracted and auto-published to the template branch.
https://github.com/cspotcode/personal-monorepo/tree/template/
Each subproject needs to follow these conventions to play nice with lerna and CI / CD.
yarn clean is nice to have. Not necessary; CI won't run it.
yarn build, if present, will be run to build the project before yarn test.
yarn test must run unit tests. It does not need to build the project.
yarn build-docs will build documentation. TODO where do the docs go? How do we publish them? Push to a branch?
git submodule foreach can run a command for each submodule.
Could be used to periodically update them to the latest master.
Although committing the latest revision to this monorepo isn't really important
as long as my working tree has checkouts at the latest master.
Issue templates:
https://github.com/cspotcode/personal-monorepo/issues/new?template=env2-shebang--bug-report.md https://github.com/cspotcode/personal-monorepo/issues/new?template=env2-shebang--bug-report.md
TODO add pull request templates
In-place templating for markdown files extend fixup.ts to generate github issue templates extend README templates to include links to github issue add a new project template
Extract fenced sections of any file? ### ### Expose results as a simple DOM and a dictionary-based hierarchy. Bonus: this can underpin a markdown fenced section rendering tool.