-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meta: post PR comment or status with a link to ecma262-compare #1891
Comments
Also, it contains the snapshot of each revision/PR.
I think this part is related to #1883 |
this is amazing and we need to integrate it |
would it be possible for the pr links to go to a page without the large header ui? we don't need to be able to switch to different prs/revisions/etc in that context (just between the commits within the pr) |
okay, I'll make the header collapse-able, and controllable with query string.
Currently, only the head commit data is created, so not possible to switch between commits within PR. |
Here's the link with the header collapsed. |
We’d want to find a way to host it ourselves, i think; but forking or transferring it to the tc39 org seems like it’d handle that. For the PR status - to start, let’s match the deploy previews and make it a “details” link; when we have a commenting solution for the deploy previews, we’ll want to combine them (ie, we probably won’t want N comments, one for each info link). |
by "host", do you mean running it on standalone server/website?
okay, I'll look into checks API. |
With checks API without GitHub App (so, authenticated with GitHub action's token), "details" link leads to a page inside GitHub, not a specified URL. to use the same way as other checks, I think I have to create GitHub App, with using some other services (maybe Heroku?) |
Hm, with the right token we should be able to set the PR status link to whatever we want, but maybe checks works differently. |
indeed, statuses API works :) I'll rewrite it to use statuses API |
Okay, looks like it's working now. But apparently posting PR status requires the user (@ecma262-compare-bot) to be a collaborator of the repository. |
Hi, I'm developing a tool for comparing the output HTML of the spec revisions and PRs
It can compare single revision, or multiple revisions,
the original purpose is to help updating implementation
Also it can compare PR change,
I hope this helps reviewing process
Those data is updated periodically (every 30 minutes for now)
Then, as part of it, I'm experimenting posting a comment to PR with the URL for it.
(currently posting comments to arai-a/workflow-test#2, instead of each PR here)
and I want to integrate it to this repository.
(tracked in arai-a/ecma262-compare#1 and arai-a/ecma262-compare#16)
Any feedback is welcome! :)
The text was updated successfully, but these errors were encountered: