@DouweM I got a report that this is still happening on GitLab.com, and going by the screen shot the user shared, his repos do comply with our naming conventions.
@roylindauer Dashes are definitely legal, we're in gitlab-ce right now :) Can you confirm both your repo path and name (they're different) only contain valid characters?
Same error here with a dot in the project name. Although I did not see any error message. Just nothing happened. Only after checking in the dev tools I found it to be the same issue.
Hi all.
First: the importer is great and was really easy to use.
I hit the name problem with various repositories where a path with spaces. The importer seemed to suggest the name of the project (with spaces) as a path (thus invalid). It would probably be nice for the importer to suggest the original path. My two cents.
I has this issue. The issue appears to report that there's a problem with my new project name (there wasn't), but it's actually because of how the project is named in BitBucket. My BitBucket project had a space in the name (though not the Git repo url). When I changed the BitBucket name within BitBucket to not include a space I was able to import into GitLab.com successfully.
As @Goodgrove already mentioned, have to rename the project name from bitbucket to make it work.
Also the To GitLab renaming is not working as expect.
Say a repo from bitbucket namespace/SomeProject, and to GitLab namespace/some-project, after imported it is still using the same namespace/SomeProject at GitLab
Similar issue here, except it doesn't seem to like brackets, which I'm unable to change as my project works off source code on github, and github is fine with the brackets. scripts/zones/East_Ronfaure_[S]/mobs/Goblintrap.lua - I'm sure the [S] is the problem. Any way around this besides renaming? Renaming would be near impossible for us.
This is still an issue. When trying to import a BitBucket repo (which has a space in its name) into GitLab, it gives me the following error message:
Error saving project: Path can contain only letters, digits, '_', '-' and '.'. Cannot start with '-' or end in '.', '.git' or '.atom'.,Path can contain only letters, digits, '_', '-' and '.'. Cannot start with '-', end in '.git' or end in '.atom',Unable to save project. Error: Path can contain only letters, digits, '_', '-' and '.'. Cannot start with '-' or end in '.', '.git' or '.atom'., Path can contain only letters, digits, '_', '-' and '.'. Cannot start with '-', end in '.git' or end in '.atom'
This error message is huge! And repetitive. GitLab needs to:
Fix the error message. It repeats itself 4 times, and it's formatted very poorly.
Fix the import. The Bit Bucket repo name is "Undergraduate Thesis" and is located at https://bitbucket.org/<username>/undergraduate-thesis, and I'm trying to import it to GitLab with the name of "undergraduate-thesis". But that's not working.
GitLab is moving all development for both GitLab Community Edition
and Enterprise Edition into a single codebase. The current
gitlab-ce repository will become a read-only mirror, without any
proprietary code. All development is moved to the current
gitlab-ee repository, which we will rename to just gitlab in the
coming weeks. As part of this migration, issues will be moved to the
current gitlab-ee project.
If you have any questions about all of this, please ask them in our
dedicated FAQ issue.
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to
rename gitlab-ce to gitlab-foss to make the purpose of this FOSS
repository more clear
I created a merge requests for CE, and this got closed. What do I
need to do?
Everything in the ee/ directory is proprietary. Everything else is
free and open source software. If your merge request does not change
anything in the ee/ directory, the process of contributing changes
is the same as when using the gitlab-ce repository.
Will you accept merge requests on the gitlab-ce/gitlab-foss project
after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in
gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git
remotes to use this new URL. GitLab will take care of redirecting Git
operations so there is no hard deadline, but we recommend doing this
as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?