Case Sensitivity in Travis-CI username and repo url's #1545
Comments
|
There's no good reason why they should be case sensitive, as far as I know. The problem is that our indexes index the cased repository, so updating the query to look for the lowercase version of the slug would most likely make it very slow. I think the best way to get around this is to add an index on |
|
Filed this as https://github.com/travis-ci/travis-web/issues/161, but I'll close that one since the issues are being consolidated here |
|
Note that URLs should be case-sensitive. (Host names are not.) |
|
Yes, but github's urls are not case sensative, causing confusion when trying to find a repo on travis-ci. |
|
URLs are case sensitive and GitHub is doing it wrong :) Can we close this? |
|
Sure. I just think that it makes it hard to find repos from github on travis-ci because you have to guess correct capitalization. |
Perhaps. But it does leave the user in a confusing mess when, say, coveralls integration doesn't work because Travis got told it was somerepository (because of being registered before a name change) and Coveralls got told it was SomeReposiTory |
Since the Travis CI APIs are case-sensitive (details: travis-ci/travis-ci#1545), the repo ID lookup will fail if the package.json repo URL does not match the case of the Github repo name. For example, a package.json URL with "https://github.com/myorg/myproject" will cause the Travis API repo ID lookup to fail if the Github repository is actually "https://github.com/MyOrg/MyProject". Relates to: semantic-release#196
Since the Travis CI APIs are case-sensitive (details: travis-ci/travis-ci#1545), the repo ID lookup will fail if the package.json repo URL does not match the case of the Github repo name. For example, a package.json URL with "https://github.com/myorg/myproject" will cause the Travis API repo ID lookup to fail if the Github repository is actually "https://github.com/MyOrg/MyProject". Relates to: semantic-release#196
Since the Travis CI APIs are case-sensitive (details: travis-ci/travis-ci#1545), the repo ID lookup will fail if the package.json repo URL does not match the case of the Github repo name. For example, a package.json URL with "https://github.com/myorg/myproject" will cause the Travis API repo ID lookup to fail if the Github repository is actually "https://github.com/MyOrg/MyProject". Relates to: semantic-release#196
|
URLs became case sensitive again about a month ago. Can we get them to be case insensitive again? My alias for opening travis based on |
I have noticed an weird thing in travis-ci repo/username paths.
Github doesn't care at all about the case of a username or repo. However, when you try and find a travis-ci repo page, you have to get the case right. If you don't, you get a very unintuitive error :
The respository at <respository with wrong case> was not foundWhen getting this error, It has made me think that travis is having an issue with my repo, not that I miscapitalized it.Is there any technical reasons that you have to have a case sensitive path?
Keep up the great work with Travis CI!
The text was updated successfully, but these errors were encountered: