Auto-generate data with ECMA262 PRs?

[bterlson]

It would be great if we could set up a travis job on the ECMA262 repo to produce the necessary files and add a comment to the PR thread with a link to the diff.

(I am not sure how to accomplish this so I am merely communicating a dream here :))

[arai-a]

Thank you for your suggestion :D

With current build script, required things to do for each PR would be following:

1. Update a ecma262 repository cloned inside ecma262-compare directory (that would contain a parent changeset of the PR)
   python build.py update
2. Download the PR's changesets and build HTML file for each changeset
   python build.py pr PR_NUMBER
3. Commit whole files changed/added with steps 1 and 2, and push it to github
4. Get an URL for the PR diff, maybe something like
   http://{USER}.github.io/ecma262-compare/#from={PARENT_HASH}&to=PR/{PR_NUMBER}/{HEAD_HASH}&id={SECTION_ID}&pr={PR_NUMBER}
   or some more optimized one, ...#pr={PR_NUMBER}, not yet implemented tho
5. Post it as a PR comment

For this use case, there may be some issue.

Whole diff generation is done in client side, and it might take long time.
specifically for PR, it might be better do it on server side, and provide the generated diff in some format.

Also, issue #2, and issue #3 might be better fixed before this use case, to avoid so long diff calculation.

[arai-a]

Now the slowness is mostly solved. maybe we could do diff generation in worker thread, but it won't affect much, as issue #3 is solved and most section won't contain so much text.

[arai-a]

One more script extract.py is added to extract information from generated HTML file.
Now it should be run after build.py update or build.py pr PR_NUMBER.
I'll merge it to build.py later.

[arai-a]

Added a dedicated URL for PR, like http://arai-a.github.io/ecma262-compare/#pr=458

[arai-a]

Now data for PRs are updated every 30 minutes (if there are more than 5 changes within 30 minutes, oldest 5 PRs are updated).
same for already merged data (up to 5 revisions per 30 minutes).

remaining part:

• trigger update on PR, instead of periodically
• post comment to PR when data is generated

[arai-a]

about triggering update on PR, this could be done by repository_dispatch [1] (haven't tried tho, it looks like usable), but there's an issue in the GitHub action,
that, it runs multiple workflows in parallel, while the update action cannot be run in parallel (it results in conflict when push)

about posting comment to PR, I guess it can be done, just by adding that API call to the action.

[1] https://help.github.com/en/actions/reference/events-that-trigger-workflows#external-events-repository_dispatch

[arai-a]

Separated into issues:

• Trigger on demand Trigger update on ecma262 push and PR #15
• Post comment to PR Post comment or status to ecma262 PR #16