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

[server] Support 'git@{host}:{user}/{repo}.git' format in context URLs #7951

Merged
merged 1 commit into from
Feb 1, 2022

Conversation

jankeromnes
Copy link
Contributor

@jankeromnes jankeromnes commented Feb 1, 2022

Description

Supports context URLs like [email protected]:gitpod-io/gitpod.git by rewriting them to https://github.com/gitpod-io/gitpod.git (without actual SSH authentication)

Related Issue(s)

Fixes #7950

How to test

  1. https://jx-ssh-context.staging.gitpod-dev.com/#[email protected]:gitpod-io/gitpod.git

Release Notes

[server] Support 'git@{host}:{user}/{repo}.git' format in context URLs

Documentation

@roboquat roboquat added release-note team: webapp Issue belongs to the WebApp team labels Feb 1, 2022
@jankeromnes jankeromnes marked this pull request as draft February 1, 2022 16:04
@codecov

This comment has been minimized.

@jankeromnes jankeromnes marked this pull request as ready for review February 1, 2022 16:18
@jankeromnes
Copy link
Contributor Author

/approve

@jankeromnes jankeromnes requested a review from a team February 1, 2022 16:19
Copy link
Contributor

@JanKoehnlein JanKoehnlein left a comment

Choose a reason for hiding this comment

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

Not sure, doesn't this raise the false expectation that we use ssh to checkout the repo?

@AlexTugarev
Copy link
Member

+1 for the change!

WSDYT of trimming to use this magic for GitHub and GitLab only for now?

Copy link
Contributor

@JanKoehnlein JanKoehnlein left a comment

Choose a reason for hiding this comment

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

I am overruled LGTM

@roboquat
Copy link
Contributor

roboquat commented Feb 1, 2022

LGTM label has been added.

Git tree hash: a4e84bb10a0a63264dc976176caabecf2810a27f

@roboquat
Copy link
Contributor

roboquat commented Feb 1, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jankeromnes, JanKoehnlein

Associated issue: #7950

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@roboquat roboquat merged commit 3240f51 into main Feb 1, 2022
@roboquat roboquat deleted the jx/ssh-context branch February 1, 2022 16:32
@AlexTugarev
Copy link
Member

@jankeromnes in addition, we could also rewrite the history/location to make the switch more transparent.

@jankeromnes
Copy link
Contributor Author

jankeromnes commented Feb 1, 2022

Not sure, doesn't this raise the false expectation that we use ssh to checkout the repo?

@JanKoehnlein Interesting point, thanks for raising it. However, I don't see any implications for cloning via HTTPS instead of SSH. To me, if cloning works, that's fantastic, but if it still fails, we're still in the same situation (i.e. we need to support something new). Did you have any specific worries in mind?

WSDYT of trimming to use this magic for GitHub and GitLab only for now?

@AlexTugarev What are your concerns with Bitbucket and GitLab Self-Managed?

in addition, we could also rewrite the history/location to make the switch more transparent.

I'd love to somehow make the switch more transparent. 💯 However, what do you mean exactly with "rewrite the history/location"?

jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
jankeromnes added a commit that referenced this pull request Feb 8, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
roboquat pushed a commit that referenced this pull request Feb 9, 2022
…@{host}:{user}/{repo}.git' format

Fixes #8097
Companion to #7951
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support '[email protected]:{user}/{repo}.git' format in context URL
4 participants