-
Notifications
You must be signed in to change notification settings - Fork 1
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
Clone Github repo using https #43
Comments
@peterwilsoncc Have you tried:
I haven't tested the mirror option so it might not work! |
@BronsonQuick In this hypothetical situation, yeah setting a custom repo works but I am wondering if we should be polite. |
I'm not sure how to setup my network to replicate this. Do you reckon this is something you could have a crack at @peterwilsoncc? |
Yeah, I'll see if I can find such a network.
…On Mon, Sep 16, 2019 at 12:16 PM Bronson Quick ***@***.***> wrote:
I'm not sure how to setup my network to replicate this. Do you reckon this
is something you could have a crack at @peterwilsoncc
<https://github.com/peterwilsoncc>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43?email_source=notifications&email_token=AAD64LY6ZOCGHLRDFLLQ5O3QJ3T6PA5CNFSM4IW4FMI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6X6ZGQ#issuecomment-531623066>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD64L52GM2PVANF74STHPLQJ3T6PANCNFSM4IW4FMIQ>
.
--
Peter Wilson, Web Developer
+61 408 031 937
peterwilson.cc
@PWCC <https://twitter.com/pwcc>
|
@peterwilsoncc If this is port-based blocking, you could also consider changing your git config to use port 443. |
I just realised this is specifically for git.wordpress.org 🤦♂ Never mind! |
Some large corporations may set up their fancy corporate firewall to block the
git
protocol, in extreme instances they may even blockssh
generally with the exception of a limited set of provides.While engineers working for these companies may think such policies are outdated and fail to consider modern development practices, it is what it is.
Fortunately
https
is usually unblocked in such cases and has been since some time in the 1990s (or early 2000s at the latest).To assist the engineers working behind such corporate firewalls, it would be handy to configure the default checkout to use
https
if a repository is not specified.git://develop.git.wordpress.org/
checkout failshttps://github.com/wordpress/wordpress-develop
The text was updated successfully, but these errors were encountered: