Added in an HTTP url for test - #445
Merged
tbranyen merged 1 commit intoMar 2, 2015
Merged
tbranyen merged 1 commit into
tbranyen merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Author
|
This is a valid HTTP repository. Weird that it fails: Error: Invalid Content-Type: text/plain; charset=UTF-8 |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Author
|
Turns out I'm not using the smart-http mode, so the headers are wrong. Once I figure that out, this should pass. |
Sorry, something went wrong.
Copy link
Copy Markdown
Collaborator
|
Github and Bitbucket both force HTTP, unfortunately. We'll HAVE to host some sort of git test server for http :/ |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Author
|
Boo ya! |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I set up an HTTP backend for my Git repositories. We can use this for now, but I'd like to have a standalone with GitHub or Bitbucket.. Relying on this URL long-term seems like a bad idea.