arai-a

For now I'll remove some old revisions. https://github.com/arai-a/ecma262-compare/commit/841c2b6c3e54143def6d676b44a33ce44961732e

Options: * Put history data in other branch, and get with GitHub API #52 * Use other hosting service than GitHub Pages, with larger limit

Hitting the issue again.

Partly because of https://github.com/arai-a/ecma262-compare/issues/66

we could trigger GC periodically, to remove obsolete revisions from PR directory

Compressed the JSON data (`sections.json`, `parent_diff.json`) by https://github.com/arai-a/ecma262-compare/commit/5366e7d313e5f2aee43caeaff928285f858de6bd, this reduces the history data from 8.2GB to 4.7GB (13MB per each revision to 7.5MB per each revision), and we can have...

Also compressed the snapshot HTML (`index.html`) by https://github.com/arai-a/ecma262-compare/commit/73e6c8a3b8fb96d55d2b817819a791f7969e633b , this reduces the history data to 1.3G (2.7M per each revision), and we can have thrice revisions in 10GB limit (~3700...

There's issue about the delay, gh-pages doesn't update immediately after the push (takes ~10 minutes). So, posting the URL in the same job for updating PR history might be misleading.

Requirement: * post at most once per each PR Mild requirement: * do not post until gh-pages get deployed

> do not post until gh-pages get deployed https://help.github.com/en/actions/reference/events-that-trigger-workflows#deployment-event-deployment > post at most once per each PR Storing a JSON file that tracks it can solve. (It's better avoid accessing...