mirror of
https://github.com/huggingface/diffusers.git
synced 2026-10-23 09:09:01 +03:00
6f2010e8bb
* Auto-reply to new model requests with Modular Diffusers guidance Points new model/pipeline/scheduler requests at building a Hub-hosted modular pipeline instead of waiting on a core PR, and asks requesters to tag @asomoza when they have something to share. Gates on the `### Model/Pipeline/Scheduler description` heading the issue form renders rather than on a label: the label the template declares does not exist in this repo, so GitHub never applies it, and template labels land after issue creation anyway. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Apply suggestion from @yiyixuxu * Tighten the new model request reply Lead with starting on the Hub and frame what follows as a support decision (work with the authors, upstream a community version, or point people at the Hub one) rather than a soft no to PRs. Trims the message by collapsing the author section and the resource list. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Link the Modular Pipelines collection in the reply Community-built model pipelines belong in the Modular Pipelines collection rather than Custom Blocks, so point the "we'll add the ones we like" line there and keep both collections in the resource list. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Recommend starting on the Hub for new models Adds a callout to the contribution guide asking model authors to get in touch on a feature request, and community contributors to coordinate there and start with a Hub repo at the same time. Points agents the same way: default to publishing a modular pipeline as remote code rather than opening a PR against src/diffusers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Apply suggestion from @yiyixuxu * Apply suggestion from @yiyixuxu * Update .github/workflows/new_model_request_reply.yml Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com> * Consolidate the Hub-first guidance into one place stevhliu noted the new callout in "Adding pipelines, models, schedulers" overlapped the last two paragraphs of the AI-assisted contributions section. Drop the community-contributor paragraph there — it is general contribution policy rather than agent-specific guidance — and point the model-author paragraph at the callout instead. Carry the custom models link over so the non-modular Hub path stays covered. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com>
44 lines
2.8 KiB
YAML
44 lines
2.8 KiB
YAML
name: New Model Request Reply
|
|
|
|
on:
|
|
issues:
|
|
types: [opened]
|
|
|
|
jobs:
|
|
reply:
|
|
name: Point new model requests at Modular Diffusers
|
|
# Match the heading the issue form renders for its first field rather than a label: template
|
|
# labels are applied after the issue is created, so `github.event.issue.labels` is empty here.
|
|
# Keep this string in sync with .github/ISSUE_TEMPLATE/new-model-addition.yml.
|
|
if: >-
|
|
github.repository == 'huggingface/diffusers' &&
|
|
contains(github.event.issue.body, '### Model/Pipeline/Scheduler description')
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
issues: write
|
|
steps:
|
|
- name: Post Modular Diffusers guidance
|
|
env:
|
|
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
GH_REPO: ${{ github.repository }}
|
|
ISSUE_NUMBER: ${{ github.event.issue.number }}
|
|
BODY: |
|
|
Thanks for the request!
|
|
|
|
**How new model support works in Diffusers**
|
|
|
|
We're a small team, and our review queue shouldn't be what decides whether a model is usable in Diffusers. With [Modular Diffusers](https://huggingface.co/docs/diffusers/modular_diffusers/overview), a pipeline can live as remote code in any Hub repo and load straight from there with `from_pretrained`.
|
|
|
|
🛠️ **Want to bring this model to Diffusers?**
|
|
|
|
Please start with a Hub repo — you don't need anything from us to do that, and people can use it immediately. From there we decide how to support it: we might work with the authors, upstream an existing community version, or just point people at the one on the Hub. The pipelines we integrate are usually the ones people are already running.
|
|
|
|
Tag `@asomoza` when you have something to share — we'll give feedback on the implementation, help get it in front of people, and add the ones we like to our hand-picked [Modular Pipelines](https://huggingface.co/collections/diffusers/modular-pipelines) collection. Tell us where you hit friction along the way, too: confusing APIs, missing docs, bugs. That feedback is worth as much to us as the pipeline.
|
|
|
|
👋 **Are you an author of the model?** We'd love to hear from you — comment here and we'll help you pick the path that fits.
|
|
|
|
📚 [Quickstart](https://huggingface.co/docs/diffusers/modular_diffusers/quickstart) · [Building custom blocks](https://huggingface.co/docs/diffusers/modular_diffusers/custom_blocks) — template repo, and how to publish to the Hub · [Modular Pipelines](https://huggingface.co/collections/diffusers/modular-pipelines) and [Custom Blocks](https://huggingface.co/collections/diffusers/modular-diffusers-custom-blocks) — examples to crib from
|
|
|
|
*This is an automated message.*
|
|
run: gh issue comment "$ISSUE_NUMBER" --body "$BODY"
|