I want to have the ability in Perforce where when one submits code, instead of getting submitted immediately, a different Perforce user gets notified so that they can review the changes to approve them before they actually get submitted.
Does any such feature exist in Perforce? Would it require a plugin? Does that feature exist in any code repo software? How would one really accomplish something like that?
There's a whole category of code review tools, such as reviewboard, Reitveld, Gerrit, etc. Here's some links: http://en.wikipedia.org/wiki/Review_Board
I would do that using shelves.
http://www.perforce.com/perforce/doc.current/manuals/cmdref/shelve.html
Related
We have a Gerrit with quite a huge namespace and projects environment and every project has different rights in a matter of code-review or workflow voting and submitting. I sometimes create a set of batch changes accross several projects and then I need reviewers to check and submit. Is there any way how to filter the search results to show only the project which the user searching them can review or submit? Currently, I usually send the results just based on the topic, but this approach still shows all the changes to the reviewers even if they don't have rights to review. Any ideas on how to do or workaround this?
This solution is not exactly what you search for but maybe it can help:
You can use the clause visibleto:'USER-or-GROUP' to match only changes that are visible to 'USER' or to anyone who is a member of 'GROUP'.
More info in Gerrit documentation here.
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.
Is it possible to get batch comments in Gitlab when doing a code review? Similar to Phabricator, where you only get one email when the reviewer makes multiple comments on your code?
We are trying to use Gitlab at work, and feel kind of spammed by the individual emails per comment.
Thanks
This is now available as per this news
There is an open feature proposal for this here.
I'm looking to use Redmine for document management. I know that Redmine is not ideal for this task but there is already a lot of content on the site so I'd like to utilize it if possible.
Redmine currently does not a have great documents module. The files we've uploaded look to be amended on that specific page and it doesn't seem to be able to move to another page (unless you download and re-upload to the proper page).
Idea 1
I see there is a Files section, which could work as a central repository (and you can upload document based on release) however, is there a way to set up a nice-looking 'front-end' page that automatically updates based on new submissions to the Files tab? I envision this front end to be a simple wiki page with the document name, a short description and a links to the file posted in the Files tab.
There are so many documents uploaded to varying pages on the Redmine site. I would only do the whole download and re-upload of files if there was a way to automatically update the 'front end' wiki.
Idea 2
I see there is a DMSF plugin for Redmine. Has anyone used this before and has is solved document management issues? I'd like to hear your feedback. Even if DMSF doesn't totally solve my issue, anything is better than what I have now.
Thanks!
In my opinion DMSF module is a perfect companion for Redmine. We have adopted it in our company. You can easily deal with document versions, webdav access, custom approval workflow, document modifications notification with the extra value of being well integrated with Redmine features (roles, dynamic links in Wiki and issue text and notes).
I would like to be able to "get information from the issue tracker" as described in the section "Getting Information from the Issue Tracker" at: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html (display a dlg box to the user when they start a commit action in svn so they can choose form a list of issues assigned to them)
I have tried finding information about a COM plugin for tortoisesvn, but have been unsuccessful in actually finding one. There are many links to pages, etc stating what is possible, but I do not want to write one and am hoping one exists.
Can anyone shed some light on this or point me to a plugin for my client?
thanks
There are example implementations of IBugTraqProvider in the contrib/ directory of the TSVN source. One's in ATL; it runs an EXE, passing (among other things) a temporary filename for the provider to write a commit message to. That EXE should talk to your issue tracker.
The other's in C#; it displays some mocked up data, but could be extended as required.
There are a couple of others: Gurtle talks to Google Code; there's one for Trac here.