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

Clone Github repo using https #43

Open
2 tasks
peterwilsoncc opened this issue Sep 15, 2019 · 6 comments
Open
2 tasks

Clone Github repo using https #43

peterwilsoncc opened this issue Sep 15, 2019 · 6 comments
Labels
enhancement New feature or request

Comments

@peterwilsoncc
Copy link
Collaborator

peterwilsoncc commented Sep 15, 2019

Some large corporations may set up their fancy corporate firewall to block the git protocol, in extreme instances they may even block ssh 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.

  • Check if git://develop.git.wordpress.org/ checkout fails
  • If failed, checkout https://github.com/wordpress/wordpress-develop
@peterwilsoncc peterwilsoncc added the enhancement New feature or request label Sep 15, 2019
@BronsonQuick
Copy link
Member

@peterwilsoncc Have you tried:

core-dev:
    mirror: https://github.com/WordPress/wordpress-develop.git

I haven't tested the mirror option so it might not work!

@peterwilsoncc
Copy link
Collaborator Author

@BronsonQuick In this hypothetical situation, yeah setting a custom repo works but I am wondering if we should be polite.

@BronsonQuick
Copy link
Member

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?

@peterwilsoncc
Copy link
Collaborator Author

peterwilsoncc commented Sep 16, 2019 via email

@rmccue
Copy link
Collaborator

rmccue commented Sep 16, 2019

@peterwilsoncc If this is port-based blocking, you could also consider changing your git config to use port 443.

@rmccue
Copy link
Collaborator

rmccue commented Sep 16, 2019

I just realised this is specifically for git.wordpress.org 🤦‍♂ Never mind!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants