Is it at all possible to let GitLab show the Changes tab when browsing merge requests? It's very annoying to check a lot of merge requests when you have to switch to Changes tab every time.
Thank you
Related
Is there any solution out of the box gitlab offers regarding sending emails for default approvers!
In other terms: if I am a default approver for a project X, then I want to receive an email whenever a new merge request is open in this project !
This is doable in bitbucket, not sure if it is the case also with gitlab.
Any help would be appreciated.
There isn't a global setting for
sending emails for default approvers
However, you can make use of Custom Notifications. They can be set at a project or a group level by the approvers themselves.
For example, you can click the bell icon in a given project and select Custom. By default Failed pipeline, Fixed pipeline, and Moved project are enabled in Custom notification events. You can then enable notification on New merge request as well.
I made a change to a widget on a page, and saved it. Now I want to revert back to the previous version of that widget. How do I do that?
If you have workflow or versioning enabled you could rollback using the Versions tab under properties of a page.
If you have not, or the version is no longer available the only thing would be looking into a Database backup.
When making a review in Azure DevOps on a pull request is there a way to get it so comments aren't immediately posted to the pull request? It's really annoying having comments go out one at a time and I want to send all of my review when I finish my review.
You can make the comments and send the notification all at one time.
All you need to do is Do Not click Comment button when you finish a comment. Leave the comment box Unsaved and move on making other comments.
When you finish all the comments, Click the 3dots on the top right corner and Click Save all comments. Then the notification emails will be sent out all at one time.
I have a problem which I am struggling to identify. It may be a Sitefinity(CMS)-problem or it may be a IIS-problem.
Explanation:
I have a external database, where the user login-information is stored. When I change my information in the external database the changes does not affect the Sitefinity-page. But if I wait for many hours OR restart the website in IIS, the changes are made and affect the sitefinitypage.
So, as far as I can see this could be either Sitefinity or IIS.
I tried to disable the Sitefinity OutPut Cache, but it did not help.
Now I want to try to do something in IIS, but I am not very familiar with IIS. Do you hae any idea of what should I do/try?
Sitefinit has caching profiles. The standard (default) one should be 20 minutes, sliding expiration if I remember correctly. Go to the page, click Title & Properties. In the dialog scroll down until you see "Advanced" seection. It's probably collapsed by default.
Expand it and see if Caching profile is anything different than "No caching". If so - make it "No caching" and save. Re-test.
This is output cache. You can think of it as saving the html page on the first request and then serving this saved copy. The cache invalidates on multiple events. For example if you publish the page - it will invalidate the cache.
Is there a way to reopen a merge request within Gitlab once it's been merged like there is with an issue?
In this example a merge request was merged before a code review and has been reverted, but it would be great to reopen the original merge request to keep the original history/discussions
There's Reopen merge request button in Gitlab (Checked with 10.3.4-ce, but appeared earlier). However it does absolutely nothing when pressed, even with commits added to the branch the merge request is tied with.
This is currently not possible. There is a feature request and someone already started working on it, but that work has stalled.
Currently the only option I see is to open a new merge request and link the old one. Probably not what you want, but easy to do, and at least the two MRs are linked.
I also looked at the API, whether it is possible to duplicate the old MR. While the API does allow you to add discussions, this is very limited. Especially as it is currently not possible to add discussions to a specific file and line number. It is not even possible to extract that information via the API.
Thus the only option to accomplish "reopening" or "duplicating" a merge request is to mess with the database or work on the merge request.