[GH-ISSUE #1369] Impact of git filter-repo on ComfyUI-Manager Functionality #564

Closed
opened 2026-10-27 21:19:03 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @ryanontheinside on GitHub (Dec 25, 2024).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1369

Hi,

I’m planning to use git filter-repo to rewrite my repository’s history to remove some large files that were mistakenly committed. Will this cause issues for users relying on ComfyUI-Manager to clone or update the repository?

Specifically:

-Does ComfyUI-Manager handle rewritten histories?
-If not, is there a way to force a fresh clone for users?

I’d appreciate any advice on ensuring a smooth transition for users.

Thanks!
Ryan

Originally created by @ryanontheinside on GitHub (Dec 25, 2024). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1369 Hi, I’m planning to use git filter-repo to rewrite my repository’s history to remove some large files that were mistakenly committed. Will this cause issues for users relying on ComfyUI-Manager to clone or update the repository? Specifically: -Does ComfyUI-Manager handle rewritten histories? -If not, is there a way to force a fresh clone for users? I’d appreciate any advice on ensuring a smooth transition for users. Thanks! Ryan
Author
Owner

@ltdrdata commented on GitHub (Dec 26, 2024):

In fact, this issue occurs intermittently across several repositories, and in such cases, the user's custom node updates will be blocked.
Currently, there is no official response to this, and the only solution is to reinstall.

In ComfyUI-Manager, resetting the custom node history installed by users is risky, so automation to address this is not applied.

In the future, it may be necessary to provide an error message and a reinstall option for cases where updates fail due to this reason.

<!-- gh-comment-id:2562715582 --> @ltdrdata commented on GitHub (Dec 26, 2024): In fact, this issue occurs intermittently across several repositories, and in such cases, the user's custom node updates will be blocked. Currently, there is no official response to this, and the only solution is to reinstall. In ComfyUI-Manager, resetting the custom node history installed by users is risky, so automation to address this is not applied. In the future, it may be necessary to provide an error message and a reinstall option for cases where updates fail due to this reason.
Author
Owner

@ryanontheinside commented on GitHub (Dec 27, 2024):

Copy that. Thank you for your reply!

<!-- gh-comment-id:2563695098 --> @ryanontheinside commented on GitHub (Dec 27, 2024): Copy that. Thank you for your reply!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Comfy-Org/ComfyUI-Manager#564
No description provided.