Skip to content

Fix Sparkle submodule URL: SSH → HTTPS for public access#1

Draft
Copilot wants to merge 2 commits into
masterfrom
copilot/fix-fork-pulling-issue
Draft

Fix Sparkle submodule URL: SSH → HTTPS for public access#1
Copilot wants to merge 2 commits into
masterfrom
copilot/fix-fork-pulling-issue

Conversation

Copy link
Copy Markdown

Copilot AI commented Apr 5, 2026

Cloning with --recurse-submodules fails for fork contributors because the Sparkle submodule uses an SSH URL pointing to a private-access GitLab repo.

Change

  • .gitmodules: Update Sparkle submodule URL from SSH to HTTPS
-url=git@gitlab.com:overtake/Sparkle.git
+url=https://gitlab.com/overtake/Sparkle.git

The GitLab repo is public; the SSH protocol was the barrier. Submodule commit pointer is unchanged, so no build impact.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • https://api.github.com/repos/sparkle-project/Sparkle/commits/8f7d1385ea7fd796a028bf116b867191586e0d86
    • Triggering command: /usr/bin/curl curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

I can't pull my fork due to a issue with https://github.com/sparkle-project/Sparkle

Created from VS Code.

Copilot AI changed the title [WIP] Fix issue with pulling fork from Sparkle repository Fix Sparkle submodule URL: SSH → HTTPS for public access Apr 5, 2026
Copilot AI requested a review from SnoElement April 5, 2026 21:18
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