Skip to content
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

Fetch live test262/Wasm results instead of relying on a triggered build #5

Merged
merged 1 commit into from
Nov 3, 2023

Conversation

trflynn89
Copy link
Member

The website currently only updates when the libjs-website repository is
updated. That is, it is not updated when new test results are published
to the libjs-data repository. Instead of setting up inter-repository GH
Actions hooks, just pull fresh data from libjs-data when loading the
website.

Example deployment at:
https://trflynn89.github.io/libjs-website/test262/

@trflynn89 trflynn89 changed the title Allow forks to deploy to GitHub pages Fetch live test262/Wasm results instead of relying on a triggered build Nov 3, 2023
@trflynn89 trflynn89 force-pushed the fresh_data branch 7 times, most recently from 850f596 to 69619e2 Compare November 3, 2023 17:04
The website currently only updates when the libjs-website repository is
updated. That is, it is not updated when new test results are published
to the libjs-data repository. Instead of setting up inter-repository GH
Actions hooks, just pull fresh data from libjs-data when loading the
website.
@trflynn89 trflynn89 merged commit d35e786 into SerenityOS:master Nov 3, 2023
1 check passed
@trflynn89 trflynn89 deleted the fresh_data branch November 3, 2023 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant