Hello @ahmedsameha1, a huge thanks for all these 0x0 environment pull requests - we really appreciate all the excellent work you've done to improve the framework's quality!

I'm reaching out because we've noticed that the volume of pull requests is putting a significant strain on our CI infrastructure. To help us keep the CI running smoothly for everyone, would you be open to bundle smaller 0x0 pull requests into single, larger pull requests? In particular, I'd consider bundling pull requests that only add a test without needing any fixes to the underlying widget itself. For example:

1. Make sure that an AnimatedSlide doesn't crash in 0x0 environment #181535
2. Make sure that an AnimatedScale doesn't crash in 0x0 environment #181481

Normally we prefer smaller pull requests, but in this case the CI overhead is proving to be significant. For more contrived 0x0 changes - for example if the widget itself needs fixes - feel keep these as standalone PRs. Thanks again for all the wonderful contributions!

@loic-sharma Do you suggest that I should do the remaining widgets that do not need fixes in the widget code in one pull request?
Should I merge these two pull requests into one, or do them in that big pull request, or leave them as is?

@ahmedsameha1 Feel free to leave the current pull requests as is. However, for future pull requests I'd consider combining multiple pull requests together until the pull request reaches ~1000 lines of code. That should be a good balance of reducing CI usage while still being reviewable.

@ahmedsameha1 Feel free to leave the current pull requests as is. However, for future pull requests I'd consider combining multiple pull requests together until the pull request reaches ~1000 lines of code. That should be a good balance of reducing CI usage while still being reviewable.

Ok, I hope that the issue will not be assigned to another contributor, as the next pull request for this issue may be after two months!

I hope that the issue will not be assigned to another contributor, as the next pull request for this issue may be after two months!

@ahmedsameha1 Ah apologies, 2 months sounds like that might be too much bundling! I'd like to make sure you're still able to land incremental progress.

What do you think of this guideline instead: combine multiple pull requests together until the pull request either updates 10 widgets, or, reaches ~1000 lines of code - whichever comes first?

And yup we can keep the issue assigned to you! :)

I hope that the issue will not be assigned to another contributor, as the next pull request for this issue may be after two months!

@ahmedsameha1 Ah apologies, 2 months sounds like that might be too much bundling! I'd like to make sure you're still able to land incremental progress.

What do you think of this guideline instead: combine multiple pull requests together until the pull request either updates 10 widgets, or, reaches ~1000 lines of code - whichever comes first?

And yup we can keep the issue assigned to you! :)

Ok.

Thanks @ahmedsameha1, and sorry I think I might have suggested that you split these up into individual PRs back when you started on this :) Thanks for being flexible.

Thanks @ahmedsameha1, and sorry I think I might have suggested that you split these up into individual PRs back when you started on this :) Thanks for being flexible.

Anyway, this made me one of the most prolific community authors in the flutter/flutter repository in 2025. It is my pleasure to be a contributor to this community, either way.

autosubmit label was removed for flutter/flutter/181535, because The base commit of the PR is older than 7 days and can not be merged. Please merge the latest changes from the main into this branch and resubmit the PR.