These are maintainers notes. "Forget-me-nots." Just ignore.
Format, lint, and run tests.
./build.sh
To build the legacy stuff.
cd ./legacy/ && ./build.ts
To build the new stuff and the legacy stuff together. Do this before a release.
./build-all.sh
Source for the site is under ./site
and compiled to and distributed from
./docs
.
./build-site.sh
This is separated so that I can isolate commits of ./docs/
builds from other
commits. ./site/src/
commits are okay to mix because those are source commits.
The ./docs/
commits are generated html, css, etc., and are quite messy next to
source commits.
WARN This is not included in
build-all.sh
. Separate./build-site.sh
commits from other source commits.
Integrated into the build.
This can be automated.
After committing the latest changes, create a tag.
git tag -a 0.0.0 -m "comment"
git push origin 0.0.0
Release it.
gh release create --generate-notes 0.0.0
If everything worked, the tag should be the latest at https://deno.land/x/proc.
Use gh release create
rather than releasing manually. The release notes are
much better and more consistent as they are based on the actual commits.