Uh oh!
There was an error while loading. Please reload this page.
fix: fix: correct grammar "same type to" → "same type as" in error messages - #14511
Conversation
160 occurrences across 158 pipeline files used the incorrect phrase "should be the same type to" instead of "should be the same type as". 2 files already had the correct form.
Hi @Ricardo-M-L, thanks for the PR! It does not appear to link an issue it fixes. If this PR addresses an existing issue, please add a closing keyword (e.g. |
Hi @Ricardo-M-L, a follow-up on the reminder above: this PR still does not link an issue it fixes. Please note that PRs without a linked issue are likely to be automatically closed 10 days after this notice. Adding a closing keyword (e.g. |
yiyixuxu
commented
Aug 30, 2026
hi @Ricardo-M-L I'm closing this per the AI-assisted contribution guidelines: https://huggingface.co/docs/diffusers/main/en/conceptual/contribution#ai-assisted-and-agentic-contributions We're seeing an increasing volume of contributions and review capacity is currently our bottleneck, so the guidelines ask for maintainer acknowledgment on an issue before a PR is opened — that's what lets us prioritize the bugs users are actually hitting. Normally we'd leave this as a suggestion and keep working with a contributor on the PR, but the volume here has made that impractical — these have come in faster than we can review them, so I'm closing all of them that you've opened rather than reviewing them individually. |
What does this PR do?
Corrects the grammar error "must be the same type to" -> "must be the same type as" in user-facing error messages across 30 files (pure message-text change, no logic).
No linked issue: pure text cleanup with no user-facing bug report. Happy to add
no-issue-neededcontext if maintainers prefer.Rebase of #13388.