https://forge-allura.apache.org/p/allura/tickets/You searched for labels:merge-reguests AND status:openenSat, 20 Oct 2018 12:34:42 -0000https://forge-allura.apache.org/p/allura/tickets/8235/Dave BrondsemaMon, 17 Sep 2018 22:16:48 -0000https://forge-allura.apache.org/p/allura/tickets/8235/https://forge-allura.apache.org/p/allura/tickets/8111/Just like tickets have an option to copy notifications to a mailing list, it would be good for merge requests to have that option also.Dave BrondsemaMon, 01 Aug 2016 18:24:01 -0000https://forge-allura.apache.org/p/allura/tickets/8111/https://forge-allura.apache.org/p/allura/tickets/7879/After a merge request is merged, it would be good to show it differently: * show original timestamp instead of timestamp of when MR was merged. * show original commits, instead of 0 commits * hide the instructions for manual mergeDave BrondsemaWed, 20 May 2015 20:42:54 -0000https://forge-allura.apache.org/p/allura/tickets/7879/https://forge-allura.apache.org/p/allura/tickets/7179/Allura should support merge requests that are specified by a branch in the current repo, in addition to the current way that requires a fork.Dave BrondsemaWed, 18 Mar 2015 23:27:08 -0000https://forge-allura.apache.org/p/allura/tickets/7179/https://forge-allura.apache.org/p/allura/tickets/6581/When creating a new Merge Request, the list of commits that will be included should be shown so that the user can verify that they are choosing the correct source & target branch. The list should update if the source or target branches are changed.Cory JohnsThu, 07 Jul 2016 20:46:44 -0000https://forge-allura.apache.org/p/allura/tickets/6581/https://forge-allura.apache.org/p/allura/tickets/6570/If a commit in a merge request references a ticket, a comment (or at least a Related link) should be added to the ticket when the merge request is created.Cory JohnsSat, 20 Oct 2018 12:34:42 -0000https://forge-allura.apache.org/p/allura/tickets/6570/https://forge-allura.apache.org/p/allura/tickets/6522/*Originally created by:* cpascual It would be very nice if the merge request discussions allowed replying by email (just as the tickets do). This would allow us have both the nice history tracking via the web interface while allowing agile mailing-list discusions for code review.AnonymousMon, 30 Sep 2013 15:11:31 -0000https://forge-allura.apache.org/p/allura/tickets/6522/https://forge-allura.apache.org/p/allura/tickets/5993/It might work well to store the downstream (fork) information as a symbolic branch name instead of a commit hash, and then resolve that at runtime, so it always includes the latest commits on that branch. Adding a comment to the merge request thread (which would also send out an email) about the new commits would be nice too, but probably a lot more work.Dave BrondsemaSat, 07 Mar 2015 00:23:34 -0000https://forge-allura.apache.org/p/allura/tickets/5993/https://forge-allura.apache.org/p/allura/tickets/5207/There are Markdown link shortcuts for commits, tickets, etc, but no way to link to a merge request. And make forward- and back-references display well.Cory JohnsFri, 06 Mar 2015 21:19:02 -0000https://forge-allura.apache.org/p/allura/tickets/5207/