Uh oh!
There was an error while loading. Please reload this page.
ci: fix build-head size failure for forks - #705
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@## main #705 +/- ##
=======================================
Coverage ? 13.36% =======================================
Files ? 68 Lines ? 3420 Branches ? 98 =======================================
Hits ? 457 Misses ? 2932 Partials ? 31 ☔ View full report in Codecov by Sentry. |
commit: |
577a44f to
fb88defComparedanielroe
commented
Jan 26, 2025
oops. too hasty an approval. still, thank you for looking at this |
schirrel
commented
Jan 26, 2025
THanks @danielroe , i am tring to see why the compare is failing, looks like it is relative to permisison/fork too, i am investigating that |
schirrel
commented
Jan 26, 2025
@danielroe i've tried one hour long all the things to find out why it was not working... even tho i was wondering if it is related to the fork, i saw some olders PR (weeks not that much) that the check passed. |
danielroe
commented
Jan 26, 2025
thank you! if you're happy to leave this PR open, I can experiment a bit with it |
schirrel
commented
Jan 26, 2025
@danielroe for sure, feel free to play around with it |
1641a70 to
ec73171Compareschirrel
commented
Jan 27, 2025
I did some testing and looks like when changing from |
schirrel
commented
Jan 29, 2025
@danielroe sorry i wrote it wrong, by:
i mean on the yml of the main branch here https://github.com/nuxt/cli/blob/main/.github/workflows/size.yml |
Uh oh!
There was an error while loading. Please reload this page.
danielroe
commented
Feb 4, 2025
weirdly, this still seems to be failing. |
schirrel
commented
Feb 5, 2025
@danielroe i believe is due the |
schirrel
commented
Feb 5, 2025
Brought back the repo info but continue to failing, nowi am changing to use sha as twk3 said in here twk3/rollup-size-compare-action#273 (comment) |
schirrel
commented
Feb 5, 2025
Looks like that: for pull_request it needs the ref to be |
Bundle Stats — create-nuxt-app size comparisonHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Bundle Stats — nuxi size comparisonHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Bundle Stats — nuxt-cli size comparisonHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Looking, I think the issue is not about the pull_request_target but in fact the token permissions required by the action. you can see it correctly commented above - so I'm not quite sure what is failing |
schirrel
commented
Feb 6, 2025
@danielroe that is real odd, i cant reason about it anymore : |
schirrel
commented
Feb 6, 2025
As you mentioned here #705 (comment) there was a check that passed https://github.com/nuxt/cli/actions/runs/13159970893/job/36725939692 I looked upon it and looks like the target commits are: The only difference after that commit on both repos is the merge of the dependabot bf6020b 🤔 it does not make sense |
danielroe
commented
Aug 8, 2025
I think this was resolved in #999. thank you for your work on this ❤️ |
🔗 Linked issue
Not a related issue but this state of Dan about the failure of the build-head from size for forks
#702 (comment)
❓ Type of change
📚 Description
Adding
repository: ${{ github.event.pull_request.head.repo.full_name }}to comparate build size for forked branchs tooFrom actions/checkout#551