You can click on the edit link for a merge request (if you have access, of course) and re-save it and that will update the merge request to include new commits.
--- ** [tickets:#5993] Merge requests should update when new commits are pushed to the fork** **Status:** open **Milestone:** unreleased **Labels:** merge-requests **Created:** Wed Mar 20, 2013 10:00 PM UTC by Dave Brondsema **Last Updated:** Wed Nov 05, 2014 10:56 PM UTC **Owner:** nobody 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. --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
