Is Pebble/Core Devices considering adding support for Git services other than GitHub in CloudPebble?
I’m thinking of services like GitLab, but also self-hosted options like Gitea (which is what I use for my private development projects).
Of course I know it’s open source and anybody can develop this and submit a PR I may look into it, but unless it’s pretty easy to do I doubt I’ll have enough time to work on it.
Just wondering if it’s already ‘on the roadmap’ or under consideration.
I know this isn’t really the topic of this particular post, but I’m curious. Now that you’re adding Git integration to Cloudpebble, it’s looking more and more like you’re trying to replicate the functionality of VS Code. Is there a reason that Core Devices switched to trying to support Cloudpebble instead of continuing to expand on the VS code extension?
VS Code (eg vscode.dev) UI is too complicated, the screen loads and there’s an infinite amount of buttons! With cloudpebble it’s all in our control and we can keep it super simple.
and other reasons as well, the github containers thing wasn’t great (if we upgraded the SDK then each person who forked the container would have to manually upgrade or create a new container).
Hope that’s a joke. Remote LLM are cost-prohibitive for single / drive-by developers, as Microsoft just demonstrated when they changed GitHub’s from a loss leader to (at best) cost neutral…
I’ll second the idea of Gitea (and other git repos) support. Ever since M$ successfully got GitHub to nine 5s of uptime, more and more people are jumping ship to alternatives
It shouldn’t even be too hard to do, sinc AFAIK Cloudpebble only performs git actions anyway. So they’d just need to deal with auth and the rest comes for free from their GitHub integration
That’s what I was thinking. I haven’t had time to dig into it yet, but I’m still planning to look into it and see if this is something I could contribute. My initial thoughts are that it’ll need a UI for configuring it and it’ll have to deal with the various authentication methods used by other systems and then, hopefully, a lot of things will “just work.”
Actually a better place to start might honestly be allowing git import from any public git URL instead of just GitHub. That might even be a matter of removing a URL check, if they’ve done things in a sensible manner.
IMO the limit on GitHub-only URLs right now does not make sense. And it will make even less sense, should Cloupebble cain the ability to authenticate with other Git services.