I recently installed GitLab to try it out and I am really enjoying it. It's very easy to install and use, still, I found an annoying "problem". I haven't yet found a way to delete Issues associated to projects.
I know that it's not a good practice to remove Issues from the system, but there are some specific occasions where this is really useful, such as when you create an Issue that makes no sense and don't want to be in the system, even after being closed.
So, my question, really simple: Is it possible to delete Issues on GitLab? If so, how can I do it?
I am using GitLab 7.2.1, on Debian wheezy.
Many thanks
It is now possible to delete issues starting with GitLab 8.6:
GitLab 8.6 released with Deploy to Kubernetes and Subscribe to Label
Delete Issues
Sometimes, simply closing an issue or merge request is not sufficient. For those times, we are now making it possible to delete issues and merge requests.
Only owners can delete issues by editing the issue or merge request and clicking, you guessed it, Delete.
At the time this question was asked, No. There is a feature request for that at: https://gitlab.com/gitlab-org/gitlab-ce/issues/2489
Now it seems possible: https://stackoverflow.com/a/36172116/895245
Click the Edit button (Pencil icon for editing the text of the issue)
Below and to the right of the text box where you can enter the description is a big red Delete button. Click it and confirm.
Personally, I find the hiding of a Delete button behind the Edit button and right next to a pretty unrelated Cancel button to be very unintuitive and weird.
You cannot do that any more.
Delete existing issue (Deprecated)
The function is deprecated and returns a 405 Method Not Allowed error
if called. An issue gets now closed and is done by calling PUT
/projects/:id/issues/:issue_id with parameter closed set to 1.
DELETE /projects/:id/issues/:issue_id
Parameters:
id (required) - The project ID
issue_id (required) - The ID of the
issue
Ref: GitLab Documentation
You can do that, but have to modify the database manually. If you have a backup, you can give it a try.
Update: Possible since GitLab 8.6.
Related
While trying to get GitLab Kanban Board to run nicely with my GitLab server I somehow managed to get myself locked out of the latter. Whenever I open the GitLab-URL now there's the message "No authentication methods configured" and no option for logging in.
Unfortunately, I don't even remember the exact settings that I was messing around with at that time, because it was a while ago and it's only now that I found the time for dealing with this problem again. IIRC one of the last things I did was to try and get OAuth working. (And I think that I was changing some settings in the web interface last, not in the settings files.)
Unable to find a solution online, one of the things I tried was to do a backup and then restore that on a different server. But the result is that I then get the same message on the new server also.
Does anyone have any idea on how to recover from this situation? Is there any way for example to enable "normal" login again by changing settings in the database?
If it's not (easily) possible to recover the whole GitLab installation, is there some way to somehow at least extract the bug report data from it? That's the data that I would be most unhappy to loose...
I'd really appreciate any help, because I'm completely at a loss right now!
You can use the Rails console to reenable your sign-in.
sudo gitlab-rails console
s = ApplicationSetting.find_by(signin_enabled: false)
s.signin_enabled = true
s.save
This will modify the rails settings directly.
As of version 10.5.X, use this instead (different ApplicationSetting key)
sudo gitlab-rails console
s = ApplicationSetting.find_by(password_authentication_enabled_for_web: false)
s.password_authentication_enabled_for_web = true
s.save
Have a simple task, but I just cannot find the quick work around, or maybe I just don't have all the info.
I have a solution (VS2012 Pro) for a SSIS project, which contains lots of dtsx packages.
When I first open the solution it pops up the enter password screen, which I want to get rid of, of course knowing the password.
My question is, is there necessary to get to the proprieties tab of each and every dtsx package and remove the password, or is there a "master setting" for the hole project? Or should I use an application which should remove the password from a command line?
Regards,
If you have a lot packages to update, I would suggest you to write a script to do it in a batch.
what I did couple years ago, I created a c# project, process each ssis package, udpate pass word and then save the package. it works fine.
API: https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.package.aspx
example: https://github.com/guoliang-dev/ssis-utils/blob/master/SSISHelper/com/liguoliang/ssis/util/DtsUtils.cs
I've just got rid of the annoying password, but the hard way. Although, the project had a security option setting, it notified me after changing it that I should manually check each and every package in order to match the security setting with the project one.
So we made a rookie mistake, One of our project team members had forgotten to commit for a couple of weeks, (some of which were vacation) but then when he did commit he did something wrong, most of the code he wrote has been overwritten with what was on the server after trying to resolve all the conflicts automatically.
So is there any way to get the code he used to have on his PC back? because a lot of work has been lost and we can't really afford to make it all again.
So just to clarify, the code which is lost is not on the server, it were his uncommitted changes on his client machine.
We are using the team foundation server and visual studio
Take a look at folder:
C:\Users\%USERNAME%\AppData\Local\Temp\TFSTemp\
In my case, searching by method name, i can recover a mistake merge =)
Nope. Code lost that never made it into source is lost. This is one of the biggest selling points of distributed version control like Git.
If your using Windows 7 or similar check for previous version of the file on his/her computer, right click the file options should be their
If you have not compiled after doing the merge, you can use DotPeek by JetBrains to decompile the assembly and get your code back
I hope this is not an incredibly stupid question.
According to what I can find online, it seems forking was added to GitLab in version 5.2. However, I can't seem to find in trace of it in the web UI. Or the help files. Or much anywhere else.
Is this perhaps a premium feature or something?
Or should it be activated/enabled somehow?
Thanks.
Also a side-note, if you haven't committed any files yet, fork option will not show to other users. you need to at least add a readme file in order fork a project.
The scenario : you have a main project at startup phase and multiple developers will be working on it. You created main project in root repo, logged out , logged with your user to for project for initial set up, fork option is not there.
Ok, I was being an idiot (sort of).
Seems if you login with a DIFFERENT user (i.e. a user who is NOT the owner of the project), the fork functionality shows up clear and plain.
Excellent then.
Props to the GitLab team - loving it!
I'm working on a website with some other people. Usually when we want to modify something, we do the change on our machine and just upload the new version with ftp, hope it'll works (or that nobody will notice it doesn't the time we correct it) and that's it.
It's already not the best way to work alone but even less to work collaboratively so I'm asking advices.
I think that a solution like svn/git/mercurial could help me. I found bitbucket which allows free private repository with mercurial. But still after, how can I upload the changes I did to the ftp and make sure the version I've on my computer is the same than the one on the server.
We are all doing it during our free time (not paid) and some people comes and leave every year so I'm looking for something free, easy to use (explain to everyone why we should use a DVCS is already hard) and which doesn't rely on a specific person.
The server we are using to host the website is a cheap one and doesn't allow the use of ssh, svn,...
Thank you
Version control will not help with the issue you are describing - namely, uploading untested changes to a production site.
What you (and your team) need, is better quality control procedures - you need a test website and a tester (QA) person. The process would be:
Make a change
Update the test website
Have the update and the whole website signed off by QA
Update the production/live site
What you will gain by using version control (CVS, SVN, Git or anything else) is recoverability - you will be able to go back to a version before any breaking change. It will still not solve the issue of "the new code broke the site".
You want scheduled releases.
Commit and update code regularly
Code freeze or develop in a branch and merge to the trunk
test on a staging environment
Find a bug goto step 1
Release
You need to understand that what represents your latest correct working build is not what's on the server but in your source repository whether that be SVN or just the file system. Anything as long as it isn't the live server! Make sure everything works locally as expected then unless the site is huge (I guess not given your situation) deploy it in its entirety as a single version.