Interesting! Maybe a csv file export from the admin panel? Best regards, Sytse Sijbrandij CEO GitLab B.V.
On Mon, Nov 10, 2014 at 2:30 PM, Drew Blessing <[email protected]> wrote: > This year our compliance auditors are requesting a list of all merge > requests with the author, merger and description. They hope to get a > 'snapshot' of our code review process and some of our changes this way. It's > part of the validation that we're following our software development > lifecycle. > > I'm considering creating a rake task that will output all merge request > information for specific projects. Is anyone else facing similar requests > from auditors? Would this rake task be helpful? If so, what output format > would be best? Obviously I could just go to the database and run a one-off > query to get this information. I'm more interested in a nicely packaged > solution like I described and would like some input before pursuing it. > > -- > You received this message because you are subscribed to the Google Groups > "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/45d3a86b-ccc6-449b-8ead-060255b5bfad%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAJTzhG8ytZ5RDTrgx94bpLcL5s6y5t%3DdYLptwx%3Duq%2B_Km9WoFQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
