upload benchmarks_generated.js for releases as part of the release workflow#911
upload benchmarks_generated.js for releases as part of the release workflow#911xabbu42 merged 1 commit intomaplibre:mainfrom xabbu42:fix-benchmarks-deploy
Conversation
|
Bundle size report: Size Change: 0 B
ℹ️ View DetailsNo major changes |
|
You can test this by adding a manual trigger to the upload benchmark yml, this way you can test that the latest is being uploaded. |
HarelM
left a comment
There was a problem hiding this comment.
This is good, please see my comment about adding a manual trigger.
|
I'm quite sure upload-benchmarks.yml is ok, as I only remove steps which where never run anyway. I'm a little bit less sure about the release workflow. I don't want to accidentally do a release :-) |
|
You can create a pre release maybe? |
|
Ok, thanks for the review. I'll check if it worked after the next release. |
|
@xabbu42 This is the output we got from the release workflow. |
|
seems to have worked ok, the only small issue I see is that we now have 2 commits against gh-pages with the exact same commit message "deploy: f47e53c". we should change the commit message for the release workflow to something like "deploy: v2.1.1". |
|
good idea. Are these warnings about missing directory and path irrelevant? |
|
also I forgot to set BENCHMARK_VERSION, so it says "main f47e53c" instead of "v2.1.1". |
|
I don't know. Perhaps I can look into it tomorrow. |
|
The warnings about missing directory are a problem with the action we use and can safely be ignored. I opened a pull request to avoid it: peaceiris/actions-gh-pages#698 |

This hopefully fixes #861.
I'm not sure how to test workflows locally so this is as yet untested.