Skip to content
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.

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

🔧 [Bug] - GitLab Server: Fork doesn't get the right SSH url when clone #2373

Open
mlaidouni opened this issue Nov 14, 2024 · 3 comments
Open

Comments

@mlaidouni
Copy link

First, thank you for all your work ❤️

What's the problem ?

I've an account of a GitLab Server called https://gitlab.mycompany.net/

image

But this GitLab server doesn't use ssh port 22, but 2222. So the ssh url to clone is ssh://[email protected]:2222/user-or-group/repository-name.git. But fork doesn't get the right SSH URL:

git-fork

Note

Is it possible to have the right ssh url please ?

Second Issue: Can't Switch back to HTTPS

See issue #2372

git-fork2

@DanPristupov
Copy link
Contributor

But this GitLab server doesn't use ssh port 22, but 2222

Yes, but how can Fork know what port your server is using?

@mlaidouni
Copy link
Author

I don't know 🤷🏼‍♂️ I know that SourceTree is able to do this, so I assume there is a way to get this information

@mlaidouni
Copy link
Author

But this GitLab server doesn't use ssh port 22, but 2222

Yes, but how can Fork know what port your server is using?

Hi @DanPristupov ! You can get it with an API request. For example: GET https://gitlab.mycompagny.net/api/v4/projects answer with a key "ssh_url_to_repo": "ssh://[email protected]:2222/mygroup/myrepo.git"

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

No branches or pull requests

2 participants