Clean Gitee File Bed🐶

The cleanup half of this pack's Gitee file-bed pair. Upload to Gitee File Bed pushes a local file to a Gitee repo and hands you back a public URL; this node is what removes it again - useful if you're using a repo as scratch storage for files that only need to be public temporarily (an image attached to one Feishu message, say) and don't want the repo quietly accumulating every file you've ever pushed through it.

What it does

Five required fields, and they mirror the upload node's addressing exactly: repo_owner and repo_name identify the repository, access_token is a Gitee personal access token with write (delete counts as a write) permission on that repo, branch is which branch to delete from, and file_path is the path of the file within the repo to remove. One output beyond that: show_help, the usage-reference text this pack attaches to most of its Gitee and Feishu nodes.

Notice there's no download_url coming back here the way there is on the upload side - this node's job is purely destructive. It removes a file; it doesn't hand you anything to do with afterward.

Where it fits

Pair this with Upload to Gitee File Bed if you're treating the repo as short-lived, disposable storage - upload, use the download_url for whatever needs a public link (a Feishu image message, say), then delete once it's served its purpose, rather than letting old uploads sit in the repo indefinitely. If you're fine with the repo growing over time and don't mind manually pruning it later, you can skip this node entirely and just never call it.

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, then pip install -r requirements.txt from inside the pack folder using ComfyUI's Python, then restart.

Same Gitee-side prerequisites as the upload node: a repo you control, and a personal access token with write access to it.

Common issues & troubleshooting

Delete fails with an auth error. Same story as the upload node - access_token needs write permission on the exact repo named in repo_owner/repo_name, and a token that's read-only or scoped to a different account will fail here.

file_path doesn't match, delete does nothing or errors. This has to be the exact path of the file as it exists in the repo, not the local path you originally uploaded from - if you're chaining this after the upload node, use file_name from that node's output (or the same file_path you used when uploading) rather than re-typing it, to avoid a mismatch.

Deleted the wrong file, or deleted something still in use. Since this is a genuine repository delete with no confirmation step in the node itself, be careful about deleting a file whose download_url might still be referenced somewhere downstream (a message already sent, a link already shared) - once it's gone, any link pointing at it breaks.