Skip to content

match parent repo protocol when forking#2434

Merged
vilmibm merged 2 commits intotrunkfrom
1056-proto
Nov 20, 2020
Merged

match parent repo protocol when forking#2434
vilmibm merged 2 commits intotrunkfrom
1056-proto

Conversation

@vilmibm
Copy link
Contributor

@vilmibm vilmibm commented Nov 19, 2020

closes #1056

when "in" a parent repo and we do a fork, check the parent's entry in remotes and make the new
fork's git protocol match accordingly.

@vilmibm vilmibm requested review from mislav and samcoe November 19, 2020 00:59
Copy link
Contributor

@samcoe samcoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link
Contributor

@mislav mislav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! Thank you for doing this 🌟

Would we also consider doing this while forking during pr create? It's also an area where users noticed that the protocol of their origin remote wasn't matched when a fork was created. It could also be a separate PR.

@vilmibm vilmibm requested a review from mislav November 19, 2020 20:03
Copy link
Contributor

@mislav mislav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome!

@vilmibm vilmibm merged commit 05a1a25 into trunk Nov 20, 2020
@mislav mislav deleted the 1056-proto branch March 9, 2021 17:28
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

Successfully merging this pull request may close these issues.

gh repo fork adds remote using https protocol even if repository was cloned through ssh

3 participants