Do we commit the coverage report files in the repository? I'd prefer to avoid it as it feels like the noise to the commit history.

Is there a way to specify where deno coverage --html output is written? If not, we should add one.

Otherwise, to remove everything from /coverage except /coverage/html, we'd have to use a complicated command like:

find /coverage -mindepth 1 -maxdepth 1 ! -name 'html' -exec rm -rf {} +

Is there a way to specify where deno coverage --html output is written? If not, we should add one.

There seems none

Otherwise, to remove everything from /coverage except /coverage/html, we'd have to use a complicated command like:

find /coverage -mindepth 1 -maxdepth 1 ! -name 'html' -exec rm -rf {} +

All raw coverage data are in the form of <uuid>.json. This can be simplified to

rm coverage/*.json

All raw coverage data are in the form of <uuid>.json. This can be simplified to

rm coverage/*.json

I get the following on my machine:

zsh: argument list too long: rm

Then maybe use:

find coverage -name "*.json" -delete

BTW I'm now not in favor of this move if we try to commit the coverage report to the repository. They will be huge noise. It duplicates the entire std source code embedded in html

This won't commit the coverage report to the repo.

It seems that files outside of coverage/html aren't uploaded to Deploy. The assets uploaded are roughly equal to the amount of files contained within coverage/html. I think this is thanks to how Deploy handles the root directory.

In other words, deleting the JSON files may not be needed.

Ping @kt3k

To keep the commit history clean, why not have a separate branch where a GitHub action auto updates it?

Maybe deploy daily?

An alternative option would be to use GitHub Pages and publish with GitHub Actions. Wouldn't even need to commit to the repo and it could update with every push to the main branch