I think it is a matter of definition of "small" and "enormous". If you have a small thing, easily comprehensible, but big enough for it to be a complete piece of work. Then probably you also have separate task for it, and the change you introduce doesn't break the build. So it the end it's just a perfect candidate for pull request.
But note the comment above mentioned a commit for variable change. Or a commit for adding some comment sentence. Nano commits they are.
Sure, tasks should be small, easy to get, easy to review. But there must be a balance. Going to extreme, both ways, doesn't do any good.
But note the comment above mentioned a commit for variable change. Or a commit for adding some comment sentence. Nano commits they are.
Sure, tasks should be small, easy to get, easy to review. But there must be a balance. Going to extreme, both ways, doesn't do any good.