8000 Updated submodules to use https:// vs git@ by smarterclayton · Pull Request #129 · deepseek-ai/DeepGEMM · GitHub
[go: up one dir, main page]
Skip to content

Updated submodules to use https:// vs git@ #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 21, 2025
Merged

Updated submodules to use https:// vs git@ #129

merged 1 commit into from
Jul 21, 2025

Conversation

smarterclayton
Copy link
Contributor

Anonymous cloning is more difficult with git@ (it requires per user
SSH keys), which makes CI automation more difficult.

I suggest reverting to using https:// as it was before #112

$ git clone git@github.com:fmtlib/fmt.git 
Cloning into 'fmt'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

@smarterclayton
Updated submodules to use https:// vs git@
91db99d 
Anonymous cloning is more difficult with git@ (it requires per user
SSH keys), which makes CI automation more difficult.

This commit reverts to using https:// as it was before deepseek-ai#112
@LyricZhao
Copy link
Collaborator

Thanks!

@LyricZhao LyricZhao merged commit c1db17e into deepseek-ai:main Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@smarterclayton @LyricZhao
0