-
Notifications
You must be signed in to change notification settings - Fork 60
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
allow ssh:// as part of the remote git URL #134
Comments
I don't have a gitea instance to test this locally, but couldn't you declare the Something like github_token=git
github_username=gituser
github_repository=klipper_trident
git_host="hal.domain.com:222"
git_protocol=ssh I cannot currently test whether the normal push via ssh to GitHub also works with an If so, I would simply update the line soon, as it shouldn't make any difference for existing users. Edit: |
The issue is that I need the if the protocol is ssh the URL is rewritten with very little control.
so what I am suggesting is the using the full ssh URL instead of the scp like URL syntax. otherwise I have manage this in the .ssh/config file, which is a possibility but the above seems like much cleaner solution. in short the URL will always be |
Also this is not a gitea issue, just a non standard ssh port issue. |
Think we are on the same page, our messages crossed 👍 |
Could you update to the latest version and test it? You should now enter the following in the .env:
We now use another new variable called |
LGTM, works fine. tried with the latest. |
fixed with 1ccd26a |
Is your feature request related to a problem? Please describe.
I have selfhosted gitea running on an on standard port "222", which means the remote URL needs to look like.
ssh://[email protected]:222/gituser/klipper_trident.git
Describe the solution you'd like
Describe alternatives you've considered
None
Additional information
If we move to just url with protocol in the front like
ssh://
it allows me to specify port in thegit_host: hal.domain.com:222
which then works well.The text was updated successfully, but these errors were encountered: