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

Update about.html to link to each test's GitHub directories instead of directly linking to README.md files. #384

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

rniwa
Copy link
Member

@rniwa rniwa commented Feb 29, 2024

No description provided.

@rniwa rniwa added v3-blocker trivial change A change that doesn't affect benchmark results labels Feb 29, 2024
Copy link
Contributor

@camillobruni camillobruni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks!

Copy link
Contributor

@camillobruni camillobruni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks!

@julienw
Copy link
Contributor

julienw commented Feb 29, 2024

Can we create the branch before merging this though? :-)

<a href="resources/todomvc/architecture-examples/preact-complex/README.md" target="_blank">TodoMVC-Preact-Complex-DOM</a>,
<a href="resources/todomvc/architecture-examples/svelte-complex/README.md" target="_blank">TodoMVC-Svelte-Complex-DOM</a>,
<a href="resources/todomvc/architecture-examples/lit-complex/README.md" target="_blank">TodoMVC-Lit-Complex-DOM</a>
Workloads: <a href="https://github.com/WebKit/Speedometer/tree/release/3.0/resources/todomvc/vanilla-examples/javascript-es5" target="_blank">TodoMVC-JavaScript-ES5</a>,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GitHub question: does this mean the branch will be named "release/3.0"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

@rniwa
Copy link
Member Author

rniwa commented Feb 29, 2024

Can we create the branch before merging this though? :-)

My plan is to merge this then create release/3.0 branch right away. That way, release/3.0 would contain the correct URLs.

@bgrins
Copy link
Contributor

bgrins commented Mar 1, 2024

My plan is to merge this then create release/3.0 branch right away. That way, release/3.0 would contain the correct URLs.

OK, that's fine

@rniwa
Copy link
Member Author

rniwa commented Mar 1, 2024

@bgrins @julienw : Could either one of you approve the change?

@bgrins
Copy link
Contributor

bgrins commented Mar 1, 2024

Done, missed that earlier.

@rniwa
Copy link
Member Author

rniwa commented Mar 1, 2024

Thank you!

@rniwa rniwa merged commit 5654961 into main Mar 1, 2024
4 checks passed
@rniwa rniwa deleted the update-about-link-github branch March 1, 2024 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
trivial change A change that doesn't affect benchmark results v3-blocker
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants