Gitlab is listing my project group folder twice (see screenshot — link above).
Each of the groups has the same project with the same ID.
I tried to rename one of the groups and the other group got renamed too.
Can anyone tell me what's going on?
Related
I am trying to create a branch linked from an issue on GitLab. The option to create a branch from the issue however is missing on this particular project. I have an access level of Maintainer on this project.
The current project I'm working on:
I have checked the other project I made a few months back on which I have exactly the same access level, the option that I'm looking for is there.
My previous project (This is a different project btw, not the source of the fork)
The difference being is that the current project I am working on is a forked version of the old repo so I could keep historical branches from the previous version of the project. I also imported the issues from the previous repo to the new one. I tried to create a new test issue but I still can't see the menu.
It seems like I configured something wrong, could you please help me identify why I cannot access this menu? Any help would be appreciated.
Thanks!
After some digging, I found that this may be a current known issue on GitLab. It only happens on forked projects similar to #VonC's answer. However it doesn't show how to resolve the issue.
To resolve the issue you have to remove the project's fork relationship found on the Settings > General > Advance. If you forked the repo from another project, you should see the Remove fork relationship button there. This essentially removes the fork relationship of the project from the original repository. Once done, the Create merge request should pop-up immediately upon refreshing the page. Do note you need an Owner access to see the Remove fork relationship option.
For more details, please refer to this issue and this solution was from here.
Check first if this is similar to issue 39778 which refers to issue
I disable the button for projects which are forked.
The context in when it references (from a fork) issue from the original project.
No "Create merge request" in that case.
I moved a git-repository to another namespace in gitlab through the 'transfer project' option in the Admin Area. I am owner/master of both namespaces.
The first time I did the transfer it took ages for the page to automatically refresh after the move; but I figured I just let it run it's course; when I clicked away to another page and then got back, nothing seemed to have happened: Project was still in the old namespace, project is not visible in the new namespace.
However in the old namespace, it now says: " repository: does not exist" in the Project info and if I go look on disk, the nameofrepository.git & nameofrepository.wiki.git are actually moved into the directory of the new namespace and are not in the old directory anymore.
Is there any way of updating/fixing this information in gitlab easily? I did restart gitlab already, but that didn't seem to help out at all.
We're running gitlab 7.5.1
We had a similar problem in GitLab 7.1.1. The move made the original repo empty but the project did not appear in the destination group. We fixed it as follows (for this purpose let's say the original project x was in group a, and it was being moved to group b):
Browse to the repositories folder on the GitLab server.
Locate the target group b and folder x (which is what we found). This meant GitLab had moved the folder but not created the project correctly.
In GitLab create a new project in group b called temp.
Rename the project folder x in group b to temp.
Check in GitLab that the project contents is now available in group b, project temp.
If all is well, in GitLab rename project temp to whatever you want it to be (probably project x).
If those instructions are a bit convoluted, the main point is getting GitLab to create a project and then overwrite the projects folder with the moved folder. Why the project does not appear I don't know, but presume it's a bug with GitLab.
Is there a way in gitlab to disable a project from showing up as a project if the user only has guest level privileges?
To clarify and add a little more detail.
I have added the ability for guest to download code but removed pretty much every privellege regarding actually using gitlab to look at the project. Which means that if the project shows up as a project to the user and they click on it gitlab returns an error. I would much rather gitlab not show the project at if the user has guest level access.
We use git submodules in our projects and we need to be able to give people the ability to clone a repo and all it submodules without giving everyone access to browse and find every project that can be a submodule or making projects public.
Currently not. But feel fee to create a PR which add's this functionality
I just installed GitLab 6.0.0 and I am now trying to create a group in order to share a common repository with other users. So I created the group and then added the users I want as owners of this group.
The problem is that the group members don't seem to be able to choose the corresponding namespace when they creating a new project.
Is this a bug? or am I missing something?
Any help is welcomed, thanks.
Best regards,
Michael Pinheiro
It looks like this bug: issue 4900
workarounds:
I should also mention that if User B now creates a Group Y, he is now able to create projects for Group X and Y. (which is a simple workaround)
The other work-around is to have the user create the project in their personal namespace first, then when the repo is created go to settings -> dangerous settings -> change namespace option.
A patch should be proposed soon to fix that bug, which seems to be related to app/models/user.rb (lines 293-295 and lines 331-333)
In subversion I'm trying to commit a project but running into an issue.
The error I get is
Illegal repository URL ''
How come I can run update, but commit on the same tree shows that?
Try this, it worked for me:
Create a folder.
Right button over folder and create repo here.
When pop up appears select create folder structure and then open folder.
When repository browser appears you see tags branch etc, right button again and create folder but now with tool tortoise.
Update you file to folder.
After some hunting around it seems that a few other people have experienced some sort of local corruption at the top level their checked out project directory which is where I was committing from.
I followed the same procedure that was used to solve those cases which is to back up the sources. Check out the project again. Finally copy the changed files back over the freshly checked out copy. Check it builds correctly. And then commit that.
It seemed to solve it for me.