Upload to Gitee File Bed🐶
Turn a local file into a public URL via a git repo
- download_url
- branch_name
- file_name
- show_help
Gitee is a Chinese GitHub-equivalent (run by OSChina), and among Chinese developers it's a very common improvised file host: push a file to a repo, get a public raw-content URL back, treat that URL like you'd treat an image-hosting link. This node automates exactly that "commit and get a public URL back" cycle - the pack's own version of a "file bed" (文件床), the same underlying need its sm.ms and imgbb image-hosting nodes cover, just via a git repo instead of a dedicated media host. Worth knowing why this option specifically exists: Gitee is fast and reliably reachable from mainland China, which some image-hosting services this pack also supports are not, always or consistently.
What it does
repo_owner and repo_name identify the Gitee repository you're pushing to, access_token is a Gitee personal access token with write permission to that repo, target_branch is which branch the commit lands on, and file_path is the local file you're uploading. That's the entire input surface - point it at a repo you control, with a token that can push to it, and a local file to send up.
Three real outputs plus the pack's usual help text: download_url (the public link to the file you just pushed - this is the actual payoff of the node), branch_name, and file_name. download_url is what you'd feed into anything downstream that needs a public link rather than a local path - this pack's Feishu image-sending nodes, for instance, or any other integration that wants a URL instead of a file on disk.
Where it fits
Reach for this specifically when something in your workflow needs a public URL for a file and you don't already have one - the alternative in this pack is its sm.ms/imgbb image-hosting nodes, and Gitee is the option worth defaulting to if you're building for users in mainland China, or if you'd simply rather manage your "file bed" as a git repo you already control than depend on a third-party image host's uptime.
Installing it
Standard pack install:
- ComfyUI Manager: search "comfyui_LLM_party", install, restart.
- Manual:
cd ComfyUI/custom_nodes && git clone https://github.com/heshengtao/comfyui_LLM_party, thenpip install -r requirements.txtfrom inside the pack folder using ComfyUI's Python, then restart.
Separate from the node install: you need an actual Gitee account, a repository you control (public, since the point is a publicly reachable download_url), and a personal access token generated with write access to that repo - Gitee's own account settings, not anything this node sets up for you.
Common issues & troubleshooting
Upload fails with an auth error. Check access_token is valid and actually has write permission on the specific repo named in repo_owner/repo_name - a token scoped too narrowly, or one generated for a different account than the repo owner, fails here.
Upload succeeds but download_url doesn't resolve publicly. Confirm the target repository is genuinely public - a private repo's raw content URL isn't reachable by anyone without the same access token, which defeats the point of using this as a public file bed.
Branch doesn't exist. target_branch has to already exist in the repo - this node commits to a branch, it doesn't create one from nothing, so a typo'd or not-yet-created branch name will fail before anything gets uploaded.
Inputs (5)
| Name | Type | Default | Description |
|---|---|---|---|
| repo_owner | STRING | — | |
| repo_name | STRING | — | |
| access_token | STRING | — | |
| target_branch | STRING | — | |
| file_path | STRING | — |
Outputs (4)
| Name | Type | Description |
|---|---|---|
| download_url | STRING | — |
| branch_name | STRING | — |
| file_name | STRING | — |
| show_help | STRING | — |