Replies: 2 comments
-
|
I would be interested too, it feels very weird that they are split. I don't see a reason why they would be. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is the sole difference the additional 3rd party provider support or is anything else going in this repo that doesn't make it into the main one? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm just wondering what's the point of having a separate repo for CLIProxyAPIPlus? I didn't understand the blurb at the top of the readme explaining the difference. Why not just have GitHub Copilot auth built into the original repo?
I ask because I maintain my own fork of CLIProxyAPI where I've been fixing lots of bugs and adding features, and I use it reguarly. It's been very reliable, and I try to keep it up-to-date with upstream from original CLIProxyAPI repo. Wondering if I should move my changes over to the Plus repo.
Beta Was this translation helpful? Give feedback.
All reactions