Skip to content

Add http protocol for Gitlab custom host #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

Merged
merged 8 commits into from
Feb 10, 2017
Merged

Add http protocol for Gitlab custom host #60

merged 8 commits into from
Feb 10, 2017

Conversation

MartinDelille
Copy link
Contributor

No description provided.

git-open Outdated

# handle SSH protocol (links like ssh://git@gitlab.domain.com/user/repo)
giturl=${giturl/#ssh\:\/\//https://}
giturl=${giturl/#ssh\:\/\//${gitlab_protocol}://}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't test this since my remote url use the following scheme: git@gitlab.mydomain.com:mygroup/myrepository.git

@ffes
Copy link
Collaborator

ffes commented Nov 23, 2016

@paulirish I would suggest to merge #56 first, then look at this one. They do conflict with each other.

@MartinDelille
Copy link
Contributor Author

@ffes As you wish!

@paulirish
Copy link
Owner

seems bad to have a source control server not on a secure connection....

git-open Outdated
@@ -93,14 +93,18 @@ else
# custom GitLab
gitlab_domain=$(git config --get gitopen.gitlab.domain)
gitlab_port=$(git config --get gitopen.gitlab.port)
gitlab_protocol=$(git config --get gitopen.gitlab.protocol)
if [ -z "$gitlab_protocol" ]; then
gitlab_protocol=http
Copy link
Owner

Choose a reason for hiding this comment

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

the default should be https, no? otherwise the docs in the readme don't make sense as setting it is redudant..

@paulirish
Copy link
Owner

@MartinDelille ive got good news and bad news. :)

good news: i'm nearly ready to merge this PR and finally get this sorted.
bad news: I edited your https branch (on your repo) which you've pointed people to.

I'm going to attempt to revert those changes to put your branch back to normal. then I'll followup with a PR to your https branch. Once accepted we'll merge that into master here. sound good?

This reverts commit b25190b.
This reverts commit 18573f8, reversing
changes made to 88a9e25.
@paulirish
Copy link
Owner

@MartinDelille k. your http branch is back as you left it. :)

@paulirish
Copy link
Owner

And PR to finalize all this is up: https://github.com/MartinDelille/git-open/pull/1

Rebase to master + default gitlab to https
@MartinDelille
Copy link
Contributor Author

Done

@paulirish paulirish merged commit 4e3aa0a into paulirish:master Feb 10, 2017
@paulirish
Copy link
Owner

All set! Thanks for everyone's patterns on this!

@paulirish
Copy link
Owner

Patience*

@ffes
Copy link
Collaborator

ffes commented Feb 10, 2017

@paulirish we do run our gitlab on our LAN, but with https so could not test really test this. I will test the current master Monday, because I use git-open every day 😉

@paulirish
Copy link
Owner

@ffes thanks! sounds good.

I've just published 1.3.0 to npm which has this PR.

iblea pushed a commit to iblea/git-open that referenced this pull request Jun 17, 2024
* Add http protocol for Gitlab custom host

* default to https

* Revert "default to https"

This reverts commit b25190b.

* Revert "Merge branch 'master' into http"

This reverts commit 18573f8, reversing
changes made to 88a9e25.

* Revert "Revert "Merge branch 'master' into http""

This reverts commit fa0e6d1.

* Revert "Revert "default to https""

This reverts commit d754476.
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.

3 participants