You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in the WooCommerce blocks project we use the compressed-size-action for tracking build size increases in pulls against the master branch.
Since we're moving to having pulls created for releases, I thought it'd be neat if there could be a signal to this action that triggers comparing the pull against the most recent release tag (non pre-release).
The benefit of this is that the release pull request would then have data included in it about the impact the entire release has on increases in build sizes from the previous release which can be hard to notice incrementally during ongoing development between releases.
This data can then be used to inform whether the size impact is more significant than expected and potentially block the release until it's dealt with.
The text was updated successfully, but these errors were encountered:
Currently in the WooCommerce blocks project we use the
compressed-size-action
for tracking build size increases in pulls against the master branch.Since we're moving to having pulls created for releases, I thought it'd be neat if there could be a signal to this action that triggers comparing the pull against the most recent release tag (non pre-release).
The benefit of this is that the release pull request would then have data included in it about the impact the entire release has on increases in build sizes from the previous release which can be hard to notice incrementally during ongoing development between releases.
This data can then be used to inform whether the size impact is more significant than expected and potentially block the release until it's dealt with.
The text was updated successfully, but these errors were encountered: