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.
Related
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?
After a server crash, the appX.git folder on the server is almost all there, object files are intact, but I Lost the appX.git/refs folder and packed-refs file. How do I recreate these references without the client files?
On the web interface it shows issues, project members but no files on the repository
Assuming there is no GitLab backup done to restore (through, for instance, gitaly-backup), one possible workaround is to:
create a new one with the different name
push back a local clone to the new one
copy the refs folder of the new one to the old incomplete one on the server
If, however, "without the client files" means there is no local clone anywhere... then there is no obvious solution.
How to take the project from one repo (where I've been given developer rights by some other person who is the master) to my own created repo (where I'm the master). I'm able to use both CMD and webstorm IDE for accessing GIT.
The action you want to perform is called 'fork' in the context of source code management (e.g git). Quoting https://docs.gitlab.com/ee/gitlab-basics/fork-project.html:
A fork is a copy of an original repository that you put in another namespace where you can experiment and apply changes that you can later decide whether or not to share, without affecting the original project.
To fork a project in GitLab, you just have to click on the 'fork' button on the project's main page.
You can read detailed steps on https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork
My new Tortoise SVN repository project should be mix of some files on my local disk and some files already part of another existing project in SVN. Regarding those (existing) files, can I simply copy them using repo browser into new project and then do check out to bring them into local working copy ? Or should I check out existing files to working folder of new project, then add new local files to it and after that add all of them to mentioned new repo project ? Or ... ?
Here are some solutions depending on your application:
if you do not want to duplicate the existing files in the repository: you should use svn:externals property (see Subversion doc and TortoiseSVN doc). This allows you retrieving in the working copy of your new project some folders coming from another location in repository (e.g. from another project). The constraint is that you can do that with entire folders, not separate files.
if you don't matter duplicating the files in the repository: in your local working copy (not in the repo browser), you should select the files you want to copy, right click and choose Context Menu → Copy from the explorer context menu. Then browse to the target folder, right click and choose TortoiseSVN → Paste. Then commit all in once. This is described here.
I have a Saas type web app, and currently have no branches. I want to have a Dev and a Main branch. I had all my project folders just under the main TFS project folder. I then created a Dev folder and moved all the sub project folders and files into it since the current code represents the latest future work compared to what is currently in production. Now I am trying to create the Main Branch from the Dev branch by the changeset that represents the current production environment.
But when now trying to branch from the Dev branch, it says that
$/Project/Dev does not exist at the specified version or you do not have permission to access it
Am I doing something wrong? Do I need to convert the Dev branch to just a folder and try again (I would try it but afraid of messing something up)? Reparent the Dev branch? Ideas?
I got this error when doing a branch by Label and the labeling was not on the same level (node) as the branch itself. Situation in TFS:
branch <-- branch
folder1
folder2
folder <-- label
If you do a find in the "find label" dialog it's on a global level and not in the branch you selected. So in this sample folder1 is not part of the label. In our case the labeling is performed by a release build that does a get on folder2 instead of the branch. That's why things are this way. The error message is not very clear.
Maybe you got the same issue, where the changeset is not part of the branch.
I ran into the same issue today. In my case I created a label for a file $/EDA/Source/Integration/ETL/RunLoad.fex using tf command line utility and using the same tf command line utility ran the branch command to create a branch from $/EDA/Source/Integration/ to $/EDA/Source/Prod/Release1 and got this error. To resolve this issue what I ended up doing is during the label creation using tf command I did create a label for the folder $/EDA/Source/Integration/ first and then to the file $/EDA/Source/Integration/ETL/RunLoad.fex using label merge option. This took care of the issue and I am able to create a branch using a label now.