Skip to content

chore: remove ghproxy.imciel.com from public mirrors - #79

Closed
EkkoG wants to merge 1 commit into
RayrenSX:mainfrom
EkkoG:chore/remove-personal-ghproxy-20261103
Closed

EkkoG wants to merge 1 commit into
RayrenSX:mainfrom
EkkoG:chore/remove-personal-ghproxy-20261103

Conversation

@EkkoG

@EkkoG EkkoG commented Nov 3, 2026 •

Copy link
Copy Markdown

Hi, I maintain ghproxy.imciel.com.

This node is intended for my own projects, devices, and a small group of users. It is not intended to be a general-purpose public GitHub acceleration service.

I recently found that the address has been included in public mirror lists and bundled into several tools, bringing request volume beyond its intended scope. I do not want this personal node to be widely promoted, shared, or redistributed as a public acceleration resource.

This PR therefore removes ghproxy.imciel.com from this project's public mirror references. Please also avoid adding it back when maintaining or synchronizing mirror lists in the future.

Thank you for your understanding and cooperation.

Changes

Remove the node from release-update mirrors and personalized DDI download mirrors.

Validation

Python AST parsing and checks that other mirror entries retain their order passed. The Windows Release build was not run: this macOS host lacks the Windows/.NET 10 toolchain. This focused mirror-list removal is submitted for review with that validation limitation.

git diff --check passed.

@EkkoG
EkkoG marked this pull request as ready for review November 3, 2026 14:16
@EkkoG
EkkoG requested a review from RayrenSX as a code owner November 3, 2026 14:16
@RayrenSX RayrenSX closed this Nov 4, 2026
@RayrenSX

RayrenSX commented Nov 4, 2026

Copy link
Copy Markdown
Owner

The mirror ghproxy.imciel.com has been removed from both the release-update download mirrors and the personalized DDI download mirrors in commit bf5db2d on main.

We have noted your request to keep this personal node out of future mirror-list updates. This removal was applied directly, so this PR was closed without merging. Thank you for letting us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants